Running as a non-administrator user
You can run the monitoring agent for Microsoft SQL Server as a non-administrator user.
About this task
Procedure
- Create a user.
- Add the newly created user in the SQL Server Login user group. The user should have sysadmin SQL Server role permission on the SQL Server. To check minimum permissions, see the https://www.ibm.com/support/knowledgecenter/SSMKFH/com.ibm.apmaas.doc/install/sql_config_agent_grant_permission_sqlserver.htm.
-
Grant Modify permission to every drive that the Microsoft SQL Server agent accesses. Complete the following
procedures to propagate the permission to all sub directories:
- Go to My Computer.
- Right-click the drive.
- Click the Security tab.
- Add the newly created user.
- Give Modify permission to the newly created user.
- Click OK. This procedure takes a few minutes to apply permission to all sub directories.
-
By using the Windows Registry, grant read access to
HKEY_LOCAL_MACHINE, and propagate the settings. Complete the following steps to propagate the settings:-
Right-click the
HKEY_LOCAL_MACHINEdirectory and select Permissions. - Add the newly created user.
- Select the newly created user.
- Select the Allow Read check box.
-
Click OK. This procedure takes a few minutes to propagate the settings
to the entire
HKEY_LOCAL_MACHINEtree.
-
Right-click the
-
By using the Windows Registry, grant the
agent-specific registry permissions according to the following list.
- If you installed a 32-bit agent on a 32-bit operating system, grant full access to the
KEY_LOCAL_MACHINE\SOFTWARE\IBMMonitoringdirectory, and then propagate the settings. - If you installed a 32-bit agent on a 64-bit operating system, grant full access to the
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Candledirectory, and then propagate the settings. - If you installed a 64-bit agent on a 64-bit operating system, grant full access to the
KEY_LOCAL_MACHINE\SOFTWARE\IBMMonitoringdirectory, and then propagate the settings.
- Right-click the directory for which you have full access and select Permissions.
- Add the newly created user.
- Select the newly created user.
- Select the Allow Full Control check box.
-
Click OK. This procedure takes a few minutes to propagate the settings
to the entire
KEY_LOCAL_MACHINE\SOFTWARE\IBMMonitoringtree.
- If you installed a 32-bit agent on a 32-bit operating system, grant full access to the
- Add a new User to the Performance Monitor Users and Users group.
- Grant Modify permission to the SQL Server data file and log file:
- The default path of the SQL Server data file is
SQLServer_root_dir\DATA, where SQLServer_root_dir is the root directory of the SQL Server instance. For example, if the root directory of the SQL Server instance isC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL, the data file path is
.C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA - The default path of the SQL Server log file is
SQLServer_root_dir\LOG, where SQLServer_root_dir is the root directory of the SQL Server instance. For example, if the root directory of the SQL Server instance isC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL, the log file path is
.C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG
- The default path of the SQL Server data file is
-
Grant full permissions to the
Candle_Homedirectory. The default path isC:\IBM\APM. - Apply local security permissions, refer Local Security Policy permissions.
- Restart the SQL Server to ensure that local security permissions are applied effectively.
-
Change the logon settings for the SQL Server agent services to the non-administrator user by
completing the following steps:
- Click Start > Administrative Tools > Services.
- Right-click the Monitoring Agent For SQL Server instance_name, and click Properties. The SQL Service Properties window opens.
- Click Log On tab.
- Click This account and type the user name.
- In the Password and Confirm Password fields, enter the password, and click OK.
- Repeat steps b to e for the Monitoring Agent For SQL Server Collector instance_name, where instance_name is the Microsoft SQL Server instance name.