Configuration of MsSqlWaitTypeTest

This test reports the number, nature, and duration of waits, thereby leading you to the specific wait types that may have contributed to a general slowdown/deterioration in server performance.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• The HOST text box, indicates the variable name of the host for which the test is to be configured.

• The PORT text box, indicates the port number through which the MS SQL server communicates. The default port is 1433.

• In the INSTANCE text box, enter the name of a specific MS SQL instance that is to be monitored. The default value of this parameter is "default". To monitor an MS SQL instance named "CFS", enter this as the value of the INSTANCE parameter. 

• By default, this test requires Sysadmin privileges to execute. This is because, by default, the test pulls out metrics uing a stored procedure named sp_monitor, which requires Sysadmin privileges for execution. The USER parameter should hence be configured with the name of a USER who has been assigned the Sysadmin role. However, if you prefer not to expose the credentials of a Sysadmin owing to security concerns, then first ensure that the test does not use the sp_monitor stored procedure. For this, set the USE SP MONITOR parameter of this test to No. Then, against the USER parameter, specify the name of a SQL user who has been assigned the Public role.

• The password corresponding to the above user has to be entered in the PASSWORD text box.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box. 

• By default, none is displayed in the DOMAIN text box. If the ‘SQL server and Windows’ authentication has been enabled for the server being monitored, then the DOMAIN can continue to be none. On the other hand, if ‘Windows only’ authentication has been enabled, then, in the DOMAIN text box, specify the Windows domain in which the managed Microsoft SQL server exists. Also, in such a case, the USER name and PASSWORD that you provide should be that of a user authorized to access the monitored SQL server.

• If the Microsoft SQL server being monitored is an SSL-enabled server, then set the SSL flag to Yes. If not, then set the SSL flag to No.

• In some Windows networks, NTLM (NT LAN Manager) may be enabled. NTLM is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. NTLM version 2 (“NTLMv2”) was concocted to address the security issues present in NTLM. By default, the ISNTLMV2 flag is set to No, indicating that NTLMv2 is not enabled by default on the target Microsoft SQL host. Set this flag to Yes if NTLMV2 is enabled on the target host.

• If the ISPASSIVE parameter is set to YES, then it means that the MS SQL server under consideration is a passive server in a SQL cluster. No alerts will be generated if the server is not running. Measures will be reported as "Not applicable" by the agent if the server is not up.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.