Database - Azure dedicated SQL pool
A dedicated SQL pool in Azure Synapse Analytics represents a collection of analytic resources that Azure provisions when you use Synapse SQL. Compute capacity for a dedicated SQL pool is expressed in Data Warehousing Units (DWU). DWU represents CPU, memory, and IO Throughput bundled as a single commodity.
Turbonomic discovers dedicated SQL pools through your Azure targets, and represents them as Database entities in the supply chain.
Synopsis

Synopsis | |
---|---|
Provides: | Analytic resources to Azure Synapse Analytics |
Consumes: | DWU and storage resources in an Azure region |
Discovered through: | Azure targets |
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 (i.e., a pool with no active connections for a specific period of time), it will immediately recommend that you suspend the pool as a cost-saving measure, and show the action in Action Center. This 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.

The Parking page lists all the dedicated SQL pools that Turbonomic discovered in your environment. From this page, you can stop a running or idle dedicated SQL pool, either on demand or according to a schedule. Stopping a pool has the same effect as suspending a pool.
The Parking page also provides options to start a stopped pool, either on demand or according to a schedule.
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 actions include the 'Idle Time' information that indicates how long a dedicated SQL pool has been idle. By default, Turbonomic will generate 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:
-
Create a dynamic group of Databases and set the 'Hours Idle' filter to
Hours Idle < = 24
. -
Create a custom Database policy, set the scope to the group that you just created, and then disable suspend actions in that policy.