LearnHealth & Safety
How To Monitor SQL Server Without Sysadmin
1 min readUpdated 6 Nov 2026
A monitoring tool that demands sysadmin is not asking for access, it is asking for an incident. Almost everything a DBA needs to see is available to a much smaller permission set.
What monitoring actually needs
Reading server state, seeing object definitions, and collecting the data the engine already exposes covers performance, waits, blocking, backups and storage.
- VIEW SERVER STATE — dynamic management views: waits, sessions, requests, cache.
- VIEW ANY DEFINITION — read object and configuration metadata.
- Read access to msdb — backup history, job history and agent activity.
- Permission to run an event session, where the environment allows it.
Why the smaller account is safer
- 1.A monitoring credential that is compromised cannot drop a database or grant itself a role.
- 2.A read-only account cannot change a setting during an incident.
- 3.Auditors accept a documented least-privilege account far more easily than sysadmin.
How to check what you are being asked for
Ask the vendor which permissions each feature needs, and ask for it in writing. If the answer is 'sysadmin makes it easier', the tool was not designed for a real environment.
Least privilege is not an obstacle to visibility. It is what lets you give a team visibility without handing them the keys.
What to remember
- Monitoring needs read permissions, not control.
- VIEW SERVER STATE plus msdb reads covers most of it.
- A small credential limits the damage of a leak.
- Ask vendors for a written permission list per feature.
