Database server - Azure SQL Managed Instance
Azure SQL Managed Instance is a scalable cloud database service with an underlying infrastructure managed by Microsoft. Turbonomic discovers SQL Managed Instances through your Azure targets, and represents them as database server entities in the supply chain.
Currently, SQL Managed Instances in Azure Government subscriptions are not supported.
Synopsis

Synopsis | |
---|---|
Provides: | Transactions to end users |
Consumes: | Database server resources |
Discovered through: | Azure targets |
Monitored resources
Configure Azure database watcher to enable the discovery of metrics for vMem, maximum concurrent sessions, maximum concurrent workers, and DB cache hit rate.
Turbonomic monitors the following resources:
-
Virtual CPU (vCPU)
Virtual CPU is the measurement of CPU that is in use.
-
Virtual memory (vMem)
Virtual memory (vMem) is the measurement of memory that is in use.
-
Storage amount
Storage amount is the measurement of storage capacity that is in use.
-
Maximum concurrent sessions
Maximum concurrent sessions is the maximum number of database connections at a time.
-
Maximum concurrent workers
Maximum concurrent workers is the maximum number of database processes that can handle queries at a time.
-
DB cache hit rate
DB cache hit rate is the measurement of Database Server accesses that result in cache hits, measured as a percentage of hits versus total attempts. A high cache hit rate indicates efficiency.
Actions
Turbonomic scaling actions aim to increase resource utilization and reduce costs while complying with business policies. Turbonomic scaling actions consider vCPU, vMem, storage amount, and IOPS utilization.
Points to consider:
-
If a SQL Managed Instance is not monitored by Azure database watcher, Turbonomic does not track vMem, maximum concurrent sessions, maximum concurrent workers, and DB cache hit rate. Consequently, Turbonomic cannot recommend vMem scaling actions, such as reducing vMem capacity.
To configure Azure database watcher, see this topic.
-
Currently, Turbonomic can recommend scaling from a General Purpose to a Next-gen General Purpose or Business Critical service tier, but not vice versa.
-
For Next-gen General Purpose service tiers:
-
According to the Azure documentation, Next-gen General Purpose service tiers are currently in preview. In Turbonomic, scale actions that involve these tiers may change as Azure changes its level of support for these tiers.
-
Actions that scale up IOPS to address congestion are recommended on the Next-gen General Purpose service tier only. Turbonomic does not recommend actions to scale storage to increase the IOPS amount.
-
If a SQL Managed Instance has more than 100 user databases, Turbonomic does not recommend scaling from a Next-gen General Purpose service tier to a Business Critical service tier. This behavior ensures compliance with resource limits enforced by Azure.
Turbonomic adds
V2
to the service tier names that display in actions and scale policies. For example,GP_V2_Gen5_4
in Turbonomic corresponds toGP_Gen5_4
in Azure.
-
Utilization charts for scale actions
Turbonomic uses percentile calculations to measure resource utilization, and drive scaling actions that improve overall utilization and reduce costs. When you examine the details for a pending scaling action on a database server, you will see charts that highlight resource utilization percentiles for a given observation period, and the projected percentiles after you execute the action.

The charts also plot daily average utilization for your reference. If you have previously executed scaling actions on the database server, you can see the resulting improvements in daily average utilization. Put together, these charts allow you to easily recognize utilization trends that drive Turbonomic's scaling recommendations.
You can set scaling constraints in database server policies to refine the percentile calculations. For details, see Scaling Sensitivity.
Non-disruptive and reversible scaling actions
All scaling actions shown in the Action Center view and Action Details page are non-disruptive and reversible.