Azure SQL Missing Indexes Test
The Microsoft Azure SQL database 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 Azure SQL 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 Azure SQL database
Agent deploying the test : A remote agent
Outputs of the test : One set of results for the Azure SQL database that is configured for monitoring
Parameters | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The host for which the test is to be configured. |
Port |
The port at which the specified Host listens. |
Database Name |
Specify the name of the Azure SQL database that is to be monitored. |
User Name and Password |
Against the User Name and Password parameters, specify the credentials of the user who is vested with DBOWNER rights to the configured Database Name. |
Confirm Password |
Confirm the specified Password by retyping it here. |
SSL |
If the Azure SQL database service being monitored is SSL-enabled, then set the SSL flag to Yes. If not, then set the SSL flag to No. |
Domain |
By default, none is displayed in this text box. If the ‘SQL server and Windows’ authentication has been enabled for the Azure SQL database being monitored, then the Domain parameter 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 monitored database exists. Also, in such a case, the User Name and Password that you provide should be that of a 'domain user' with DBOWNER rights to the configured Database Name. |
IS NTLMv2 |
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, this flag is set to No, indicating that NTLMv2 is not enabled by default for the target Microsoft Azure SQL database. Set this flag to Yes if NTLMv2 is enabled for the target database. |
User Seeks DD Count |
By default, this parameter is set to 10. This means that, by default, the detailed diagnosis of the Missing indexes by user seeks measure of this test, will report only the top-10 missing indexes in terms of the number of 'seek' operators that were run for queries associated with those missing indexes. If you want, you can increase or decrease this value, depending upon how many missing indexes you want to see in the detailed diagnosis. |
Avg User Impact Percent DD Count |
By default, this parameter is set to 10. This means that, by default, the detailed diagnosis of the Missing indexes by user impact measure of this test, will report only the top-10 missing indexes in terms of the percentage by which the addition of those indexes will reduce query cost. If you want, you can increase or decrease this value, depending upon how many missing indexes you want to see in the detailed diagnosis. |
Detailed Diagnosis |
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:
|
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 missing indexes with high user impact. |
Number |
Use the detailed diagnosis of this measure to view the top-10 (default) missing indexes in terms of the estimated impact of the addition of those indexes - i.e., in terms of the percentage by which the addition of those indexes will reduce query cost. This will help you identify the indexes that are worth adding. |
Missing indexes based on user seeks |
Indicates the number of. missing indexes with high user seeks. |
Number |
Use the detailed diagnosis of this measure to view the top-10 (default) missing indexes in terms of the of the number of 'seek' operators that were run for queries associated with those missing indexes. This will help you identify the indexes that are worth adding. |