Using Query Store with least privileges instead of db_owner to achieve Separation of Duties

This post has been republished via RSS; it originally appeared at: SQL Server articles.

When using the Query Store in a production environment, sometimes customers need to delegate very specifically who can do what in terms of Performance Analysis and/or Tuning.

In this article we will demonstrate, how customers can segregate the typical activities around the Query Store and delegate minimal sets of permissions to groups of users that are mandated to certain tasks.

 

The article is published here on the Azure SQL Blog: Using Query Store with least privileges instead of db_owner to achieve Separation of Duties

 

QueryStore_ForcePlan_Permission_Error_m.jpg

Leave a Reply

Your email address will not be published. Required fields are marked *

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.