Default Parameters for MsSqlIndexFragTest

This test scans the indexes on an MS SQL server for high and very high levels of fragmentation based on configured thresholds, and reports the count of fragmented indexes.

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

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

  Note:

  This test is resource intensive. Therefore it is better to execute this test once in 24 hours.

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

• Indicate the password of the specified USER in the PASSWORD text box.

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

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

• Specify a comma-separated list of tables, the indexes of which need to be checked for fragmentation in the OBJECT NAME text box. Every table name should be specified in the following format: <DisplayName>:<schema_name>.<table_name>, where schema_name refers to the name of the table owner, and table_name refers to the name of the table. The DisplayName in your specification will appear as the descriptor of this test. For instance, to monitor the indexes of the alarm and history tables owned by user admin, your specification would be: AlarmMon1:admin.alarm,AlarmMon2:admin.history. To monitor all tables in a schema, the specification would be of the following format: <DisplayName>:<schema_name>.*. For example, to monitor all the tables in the admin schema, your specification would be: AlarmMon:admin.*.

• Specify the time period upto which a query has to wait to obtain the required result set from this database in the QUERYTIMEOUT text box. The default value of this parameter is 30. If the query is not successful or if the query waits for a time period exceeding the specified time limit, the test will automatically kill the query.

• Provide the limit (in percentage) of fragmentation above which an index is termed as a highly fragmented index in the HIGHFRAGMENTLIMIT text box. By default, the value specified here is 30. This means that if 30% or more of a monitored index is found to be fragmented, then such indexes are counted as highly fragmented indexes.

• Provide the limit (in percentage) of fragmentation above which an index is termed as a very highly fragmented index in the VERYHIGHFRAGMENTLIMIT text box. By default, the value specified here is 50. This means that if 50% or more of a monitored index is found to be fragmented, then such indexes are counted as very highly fragmented indexes.

• If the value chosen against the ISPASSIVE is set to YES, then the Oracle server under consideration is a passive server in an Oracle 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 necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing default configurations of tests, the values with "$" indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to "xyz" and $port will be changed to "80" when configuring a test.