Azure Database (classic) Test

Microsoft Windows Azure SQL Database is similar to an on-premises Microsoft SQL Server and extends the SQL Server database capability to the cloud. Azure SQL Database lets you provision and deploy relational database solutions to the cloud, including many benefits such as, rapid provisioning, scalable, high availability and minimal maintenance overhead.

Maintaining Azure SQL database on the cloud is easy to manage, with less effort, because of the complete infrastructure provided by Microsoft System Center. Though the Azure SQL database can be easily managed, it is also essential to keep track on the day-to-day performance of the Azure SQL database. To achieve this, administrators may use the Azure Database (classic) test.

For each Azure SQL database instance, this test reports the current state and also the resource utilization. Using this test, administrators can identify the Azure SQL database that is improperly sized with CPU, memory and I/O resources.

This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick Microsoft Azure as the Component type, Performance as the Test type, choose this test from the disabled tests list, and click on the < button to move the test to the ENABLED TESTS list. Finally, click the Update button.

Target of the Test: Microsoft Azure

Agent deploying the test: A remote agent

Output of the test: One set of results for each Azure SQL Database instance of the target Microsoft Azure being monitored

Descriptor: Azure SQL Database instance

  1. TEST PERIOD - How often should the test be executed
  2. Host– The host for which the test is being configured
  3. SUBSCRIPTION ID- Specify the GUID which uniquely identifies your subscription to the target Microsoft Azure that is to be monitored.
  4. CERTIFICATE PATH - In order to collect metrics from the target Microsoft Azure, the eG agent communicates via Microsoft Azure Service Management API Requests. By default, a management certificate is required to authenticate Microsoft Azure Service Management API Requests. The Management certificate should be associated with the subscription ID. The management certificate can be created on your own or you can request Microsoft Azure portal to create a certificate on behalf of you. Prior to creating a management certificate, you have to create a keystore. The steps for creating a management certificate and the keystore is discussed elaborately in Section 1.1. The created keystore will reside in the <JAVA_INSTALL_DIR>\jre7\bin folder. Specify the exact path to the keystore file in this text box. If you have requested Microsoft Azure portal to create the management certificate, then, specify the exact path on which you have stored the keystore file. For example, if the keystore file created is WindowsAzureKeyStore.jks and if you have stored it in D:\Azure folder, then specify the CERTIFICATE PATH as D:\Azure\WindowsAzureKeyStore.jks.
  5. CERTIFICATE PASSWORD - Specify the password that is provided while creating the keystore in this text box.
  6. confirm password - Confirm the password by retyping it here.
  7. DATABASE NAME - Specify the name of the database to which the target Microsoft Azure is connected to.
  8. USERNAME - Specify the name of the user who is authorized to access the database to which the target Microsoft Azure is connected to.
  9. password - Specify the password corresponding to the USERNAME here.
  10. CONFIRM PASSWORD - Confirm the password by retyping it here.
  11. 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.
  12. detailed diagnosis - 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 for a particular server, choose the On option 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.

Measures reported by the test:

Measurement Description Measurement Unit Interpretation

Status

Indicates the current status of this database instance.

 

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
Created 1
Limited 2
Offline 0

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the current status of this database instance. The graph of this measure however, represents the status of a server using the numeric equivalents only - 0 to 2.

The detailed diagnosis of this measure if enabled, lists the Server name on which the database instance is hosted, the location of the server, status of the server and the current edition of the server.

Total size

Indicates the maximum size allocated to this database instance.

MB

 

Used size:

Indicates the amount of space that is already utilized in this database instance.

MB

If the value of this measure is close to the Total size measure, then it indicates that the database instance is running short of space. Administrators should either clean the database or provide additional resources.

Free size

Indicates the amount of space that is available for use in this database instance.

MB

A high value is desired for this measure.

Storage utilization

Indicates the percentage of space utilized in this database instance.

Percent

A value close to 100 for this measure denotes that the database instance is running short of space.

CPU utilization

Indicates the average percentage of CPU utilized by the service of this database instance.

Percent

 

Avg physical data reads utilization

Indicates the percentage of physical data that is read from this database instance.

Percent

 

Avg log writes utilization

Indicates the percentage of logs written to this database instance.

Percent

 

Avg memory utilization

Indicates the percentage of memory utilized by this database instance.

Percent

A high value for this measure is a cause of concern, If the value of this measure is close to 100, then administrators should either increase the memory limit of the database or free up the available resources.

Successful connections

Indicates the number of successful connections to this database instance.

Number

 

Failed connections:

Indicates the number of connections that failed to establish on this database instance.

Number

 

Terminated connections

Indicates the number of connections that were terminated on this database instance.

Number

 

Deadlock connections

Indicates the number of connections that experienced deadlock on this database instance.

Number

Ideally, the value of this measure should be zero. If a sudden/gradual increase in the value of this measure is noticed, then administrators should query the database to identify when exactly the deadlocks occurred.

Throttled connections

Indicates the number of connections that were throttled on this database instance.

Number

Throttling is a mechanism used by Azure SQL Database to prevent the server from becoming overloaded and unresponsive. It ensures that all users receive an appropriate share of resources and that no one monopolizes resources; Azure SQL Database may close or "throttle" subscriber connections under certain conditions. Too many connections that were throttled may often lead to performance bottleneck. Therefore, the value of this measure should be zero.

Throttling long transaction

Indicates the number of long running transactions on this database instance.

Number

A low value is desired for this measure. A sudden/gradual increase in the value of this measure may decrease the performance of the database as the database locks will be retained by the transactions.