Database - Azure dedicated SQL pool

Monitored resources

Turbonomic monitors the following resources:

• DWU

  DWU (Data Warehousing Unit) is the measurement of compute capacity for the dedicated SQL pool. DWU represents CPU, memory, and IO Throughput bundled as a single commodity.

• Storage amount

  Storage amount is the measurement of storage capacity that is in use.

• Connection

  Connection is the measurement of database connections utilized by applications.

Suspend actions for dedicated SQL pools

When Turbonomic analysis discovers an idle dedicated SQL pool, it immediately recommends that you suspend the pool as a cost-saving measure. An idle dedicated SQL pool has no active connections for at least one hour (see the next section for instructions on adjusting the time period).

Controlling the generation of suspend actions

Suspend actions include the 'Idle Time' information that indicates how long a dedicated SQL pool has been idle. By default, Turbonomic generates suspend actions if dedicated SQL pools have been idle for at least one hour.

You can control the suspend actions that Turbonomic generates, based on your preferred idle time value.

For example, if you want Turbonomic to only generate suspend actions for dedicated SQL pools that have been idle for at least one day, perform these steps:

1. Create a dynamic group of Databases and set the 'Hours Idle' filter to Hours Idle < = 24.

2. Create a custom database policy, set the scope to the group that you just created, and then disable suspend actions in that policy.

Cost impact of suspend actions

A suspend action stops the compute instance for the SQL pool, but keeps storage running. In the Action Details page for a specific action, the compute cost is 0 (zero) after suspension, while storage cost remains the same.

To calculate the current compute cost, Turbonomic retrieves the hourly on-demand cost from Azure and then multiplies the result by 730, which represents the number of hours per month that the product uses to estimate monthly costs.

If a currently idle pool is not suspended and is subsequently discovered as active, Turbonomic removes the suspend action attached to it.

Suspend and parking actions

The Parking page lists all the dedicated SQL pools that Turbonomic discovered in your environment. From this page, you can stop a dedicated SQL pool temporarily as a cost-saving measure. Stopping a dedicated SQL pool has the same effect as suspending a dedicated SQL pool.

The Parking page also provides the option to start a stopped dedicated SQL pool. Turbonomic analysis, however, does not generate a subsequent action to start a suspended dedicated SQL pool. You can start a suspended dedicated SQL pool from the Parking page or from your cloud provider.