SQL Azure Missing Indexes Test

Microsoft SQL Azure database server allows you to put indexes on table columns, to speed up WHERE and JOIN statements on those columns. If a SQL query takes longer (much longer) to complete, it could be because one/more of these indexes are ‘missing’. When the query optimizer optimizes a query, it identifies those indexes it would have liked to have used but were not available - these are called ‘missing indexes’. With the help of the SQL Azure Missing Indexes test, you can be promptly alerted when the query optimizer finds one/more ‘missing indexes’. Besides reporting the count of the missing indexes, the test also reveals which queries require these indexes, thus enabling you to quickly initiate index creation and query optimization.

Target of the test : A Microsoft SQL Azure database server

Agent deploying the test : An external/remote agent

Outputs of the test : One set of results for each database instance of the target Microsoft SQL Azure database server being monitored.

Configurable parameters for the test
  1. Test period - How often should the test be executed
  2. Host - The host for which the test is to be configured.
  3. ssl – 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.
  4. instance - In this 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 an Microsoft SQL instance named “CFS”, enter this as the value of the INSTANCE parameter.
  5. USER – Provide the name of a SQL user with the view server state role.
  6. password - The password of the specified user.
  7. confirm password - Confirm the password by retyping it
  8. domain - 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.
  9. isntlmv2 - 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.
  10. ISPASSIVE – If the value chosen is yes, then 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.
  11. REPORTMANAGERTIME – By default, this flag is set to Yes, indicating that, by default, the detailed diagnosis of this test, if enabled, will report the shutdown and reboot times of the device in the manager’s time zone. If this flag is set to No, then the shutdown and reboot times are shown in the time zone of the system where the agent is running(i.e., the system being managed for agent-based monitoring, and the system on which the remote agent is running - for agentless monitoring).
  12. To make diagnosis more efficient and accurate, the eG Enterprise 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 for a particular server, choose the On option. 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 normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Missing indexes

Indicates the total number of missing indexes found in the queries that are currently executing on this database instance.

Number

The detailed diagnosis of this measure reveals the tables and the specific columns in those tables that are missing indexes. If the missing indexes are adversely impacting query performance, then database administrators can use this information to decide on the ideal approach to improving query performance - should new indexes be created? Or should queries be optimized to use existing indexes?

Missing indexes based on user impact

Indicates the number of times the resources of this database instance were impacted due to user queries when the indexes were missing.

Number

 

Missing indexes based on user seeks

Indicates the number of times the missing indexes of this database instance appeared in the result set of the queries based on user requests.

Number