A few weeks ago I was with a customer giving them guidance on how to setup the management pack for SQL, and the three accounts required where a problem for them, they told me it was to complicated because of how their account management process works.
This is a common request among customers so I thought it was a good idea to share this configuration with the community, so here are the permissions required to use a single account scenario for the SQL management pack Run As Accounts.
- Add user to the following local security groups>
- Perfomance Monitor Users
- Event Log Readers
- In SQL Server Management Studio grant the following privileges to the user:
- VIEW ANY DEFINITION
- VIEW SERVER STATE
- VIEW ANY DATABASE
- Map the user login to the msdb database and any other you want to monitor.
- Add the user login to the msdb database with the SQLAgentReaderRole.
- Add the user login to the msdb database with the PolicyAdministratorRole.
- Restart the healthservice.exe on the SQL Server.
Hope this helps with your SQL management pack setup.