Agents Administration - Tests
 

Configuration of MsSqlBlockerTest

The MsSqlBlockerTest monitors the number of root blocker processes in a database. 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 Microsoft SQL instance that is to be monitored. The default value of this parameter is "default". To monitor a Microsoft SQL instance named "CFS", enter this as the value of the INSTANCE parameter. 

  • If a Microsoft SQL server 7.0/2000 is monitored, then provide the name of a SQL user with the Sysadmin role in the USER text box. While monitoring a Microsoft SQL server 2005/2008 on the other hand, provide the name of a SQL user with the CONNECT SQL, VIEW ANY DATABASE, PUBLIC ROLE, VIEW ANY DEFINITION and VIEW SERVER STATE roles.

  • 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.

  • If the ISPASSIVE parameter is set to YES, then it means that the Microsoft 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.

  • 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.

  • Specify the minimum number of sessions a process should block for this test to count that process as a root blocker against the BLOCKED SESSION COUNT parameter. For instance, if you specify 10 here, it indicates that the Number of rootblockers measure reported by this test will include only those processes that are blocking 10 or more sessions.

  • If a process is blocked for or beyond the duration (in seconds) specified against the MAX BLOCKING TIME (SECS) parameter, then this test will count that process as a process that has been blocked for the maximum time. The details of such processes will then be captured and displayed as part of the detailed diagnosis of the Max waiting time measure. For example, if you specify 120 seconds here, then the detailed diagnosis of the Max waiting time measure will display the details of all processes that were blocked for 2 minutes and above.

  • The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.

  • To make diagnosis more efficient and accurate, the eG system embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test, by default, for a particular server-type, choose the Onoption against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability

    • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

  • 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.