SQL Server permissions

Create the login that Scops uses on a SQL Server instance, and give it the permissions that Scops needs to read the instance.

Choose how Scops signs in

Sign in withThe account
SQL Server loginA login with SQL Server Authentication. The instance must allow SQL Server Authentication (mixed mode).
Windows accountA Windows account that Scops keeps as a credential, written DOMAIN\user, user@domain or MACHINE\user. Or Scops service account: the account of the Scops service, with no password kept.

With a Windows account, a SQL Server on the machine where Scops runs always sees the Scops service account. For that instance, select Scops service account or a SQL Server login.

Scops opens its sessions in master, with the program name Scops. The permissions let Scops read. They do not let it change data or settings, and the login needs no server role.

Create the login

  1. Connect to the instance as a member of sysadmin.

  2. Create the login. For a SQL Server login:

    CREATE LOGIN [scops_monitor] WITH PASSWORD = N'<password>';

    For a Windows account:

    CREATE LOGIN [DOMAIN\svc_scops] FROM WINDOWS;
  3. Give it the required permissions, and the optional permissions if you want the Agent jobs.

  4. In Add Database, select the credential and click Test Connection.

If a Windows account gets in only through a Windows group, the script of the test creates a login for the account first.

Required permissions

Without one of them, you cannot add the instance. The test counts the missing ones, and Show Script gives their script.

PermissionVersionUsed for
VIEW SERVER STATE2017, 2019Sessions, waits and query statistics.
VIEW SERVER PERFORMANCE STATE2022 and laterSessions, waits and query statistics.
CONNECT ANY DATABASEAllThe inside of each database: files, log, Query Store, backups.
VIEW ANY DEFINITIONAllFile sizes and object names.
VIEW ANY ERROR LOG2022 and laterThe error log.
EXECUTE on master.sys.xp_readerrorlogAllThe error log, read from where the last reading ended (Log Watch). The login needs a user in master.

On SQL Server 2022 or later:

USE master;
GRANT VIEW SERVER PERFORMANCE STATE TO [scops_monitor];
GRANT CONNECT ANY DATABASE TO [scops_monitor];
GRANT VIEW ANY DEFINITION TO [scops_monitor];
GRANT VIEW ANY ERROR LOG TO [scops_monitor];
CREATE USER [scops_monitor] FOR LOGIN [scops_monitor];
GRANT EXECUTE ON sys.xp_readerrorlog TO [scops_monitor];

On SQL Server 2017 or 2019:

USE master;
GRANT VIEW SERVER STATE TO [scops_monitor];
GRANT CONNECT ANY DATABASE TO [scops_monitor];
GRANT VIEW ANY DEFINITION TO [scops_monitor];
CREATE USER [scops_monitor] FOR LOGIN [scops_monitor];
GRANT EXECUTE ON sys.xp_readerrorlog TO [scops_monitor];

Optional permissions

SELECT on five tables of msdb, with a user in msdb: sysjobs, sysjobhistory, sysjobactivity, sysjobsteps and sysjobschedules. Scops reads the SQL Server Agent jobs, their schedules and their history with them.

Without them, the test passes, and the Agent jobs on Health Check show Not read.

USE msdb;
CREATE USER [scops_monitor] FOR LOGIN [scops_monitor];
GRANT SELECT ON dbo.sysjobs TO [scops_monitor];
GRANT SELECT ON dbo.sysjobhistory TO [scops_monitor];
GRANT SELECT ON dbo.sysjobactivity TO [scops_monitor];
GRANT SELECT ON dbo.sysjobsteps TO [scops_monitor];
GRANT SELECT ON dbo.sysjobschedules TO [scops_monitor];

Run the grant script

  1. In Add Database or Edit Database, click Test Connection.

  2. If permissions are missing, click Show Script. The Grant Script window opens.

  3. Select a tab: Monitoring has the required permissions, and Agent Jobs the optional ones.

  4. Click the copy button. Ask a member of sysadmin to run the script on the instance.

  5. Click Test Connection again.

Each script has only the missing permissions, for the login that you tested. A tab shows only when it has statements to run. The script also creates the users in master and msdb that the login does not have.

The test finds a permission in all its forms: direct, through a role or a Windows group, through sysadmin, or through a wider permission.

Fix a missing permission

When a permission goes away later, the area of Health Check that needs it shows Not read and why. If a grant is the cause, the area shows the script.

  1. On the Databases page, right-click the instance and select Edit Database.

  2. Click Test Connection, then Show Script.

  3. Ask a member of sysadmin to run the script.

The next check reads the area again.

Encryption

The connection is always encrypted.

SettingWhat it does
MandatoryThe default. Encrypted after the first exchange. Every supported version takes it.
StrictEncrypted from the first byte, with the certificate always checked. SQL Server 2022 or later.
Trust server certificateWith Mandatory only. Turn it on for a server that uses a certificate it made itself.
Name in certificateThe name on the server certificate, if the host is written in a different way, such as an IP address or an alias.

Updated November 22, 2026