Required Accounts and Permissions

SQL Elements connects to registered SQL Server instances and their host computers to collect information. The collection service requires permissions to connect and gather information using SQL and WMI connection credentials.

Depending on the level of access and actions you want SQL Elements to perform on your environment, you should check you have the following permissions in each account:

AccountActionPermissions required
Windows User AccountTo install SQL Elements componentsWindows Administrator permission on the Target computer

To create and access the SQL Elements repository databases

  • Create Database Rights on the target SQL Server Instance
  • Read and write privileges on the SQL Elements Repository Databases



SQL Server login account

For most SQL queries

VIEW SERVER STATE

VIEW ANY DATABASE

VIEW ANY DEFINITION

To monitor database information

ALTER ANY DATABASE server level permission or

CREATE DATABASE in the master database

For DBCC CHECKDBsysadmin server roles
WMI accountTo access remote WMI dataAdditional rights on a group that has been given remote access


Discovery scan permissions requirements

Discovery ScanPermissions
WMIUser should be member of Performance Monitor Users group, and this group should have permissions to Remote access ROOT\cim2 namespace on targeting machines.
Registry Check

Access the computer from the network, Remote access to the registry, Remote Registry Service must be running on targeting machine and user must be granted access to "SYSTEM\\CurrentControlSetServices" and "SYSTEM\\CurrentControlSetServices" subkey’s.

Service Control Manager

Users should have GENERIC_READ , SC_MANAGER_CONNECT , SC_MANAGER_ENUMERATE_SERVICE rights.

TCP ProbeNo additional permission required.
SQL Server Resolution ServiceNo additional permission required.

Tip

Idera suggests that you provide SQL connection credentials with "sysadmin" server roles if you want to be able to collect all information from your environment.

For more information on how to solve connection problems with WMI, click here.

  • No labels