Agents Administration - Tests
 

Default Parameters for MsSqlSpaceTest

This test reports statistics pertaining to the space usage in a Microsoft SQL server database.

Note:

Note that this test will report metrics only for Microsoft SQL Server 2008 R2 (and above).

This page depicts the default parameters that need to be configured for the MsSqlSpaceTest.

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

    • Note:

    Frequent execution of this test could cause the Microsoft SQL server to incur high operational overheads, especially when the load on the server is very high. Therefore, by default, the TEST PERIOD will be set to 30 minutes.

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

  • Provide the name of a SQL user with the Sysadmin role. However, if you do not want to expose the credentials of a Sysadmin, then create a special user for this purpose on each of the databases to be monitored, and make sure that you assign any of the following privileges to that user:

    • Assign the db_datareader privilege to that user in each of the databases to be monitored; (OR)

    • Assign the PUBLIC role to that user, and grant execute permission to that user for the sp_spaceused procedure in every database to be monitored.

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

  • In the EXCLUDEDB text box, provide a comma-separated list of databases for which the space computation need not be done. For example - the temp database. The default value is ‘none’.

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

  • By default, the USEPERFMON flag is set to Yes, indicating that this test uses the Windows Perfmon utility by default to pull out the metrics of interest. To instruct the test to use queries for metrics collection and not Perfmon, set this flag to No. Typically, when monitoring a Microsoft SQL server in an agent-based manner, its best to go with the default setting - i.e., use Perfmon for metrics collection. However, when monitoring the Microsoft SQL server in an agentless manner, its ideal to use queries instead of Perfmon to collect the required metrics. In such cases, set this 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 value chosen against ISPASSIVE is YES, then the server under consideration is a passive server in a 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.

  • Once the above value is provided, click on the UPDATE button to register the changes made.

Note:

If multiple tests associated with a component share the same set of parameters, then, when one of tests is reconfigured, eG will automatically update the other tests (related to that component) with the changes. However, the Microsoft SQL server is an exception to this rule. When an Microsoft SQL server-related test is reconfigured, then the changes so made will be applied to all the tests except the MsSqlSpaceTest. This test will therefore have to be reconfigured separately. Similarly, changes made to the MsSqlSpaceTest will not automatically affect the configuration pertaining to the other Microsoft SQL server-related tests.