# Business Critical tier on non-production SQL instance Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/business-critical-tier-on-non-production-sql-instance Non-production environments such as development, testing, or staging often do not require the high availability, failover capabilities, and premium... By: PointFive Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Business Critical Tier on Non-Production SQL Instance The short version Non-production environments such as development, testing, or staging often do not require the high availability, failover capabilities, and premium storage performance offered by the Business Critical tier. PointFive Research Cloud cost research at PointFive Azure service [Azure SQL](https://www.pointfive.co/efficiency-hub/cloud-services/azure-sql) Category [Databases](https://www.pointfive.co/efficiency-hub/service-category/databases) Reference CER-0053 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. Running these workloads on Business Critical unnecessarily inflates costs. Choosing a lower-cost tier like General Purpose typically provides sufficient performance and availability for non-production use cases, significantly reducing ongoing database expenses. ## Billing model The pricing dimensions that drive this cost. Azure SQL Database instances are billed based on the selected service tier, compute size (vCores), and storage consumption. The Business Critical tier provides the highest availability and performance, using additional replicas and premium storage, but comes at a significantly higher cost compared to lower tiers like General Purpose. Selecting an unnecessarily high tier for non-production workloads leads to elevated expenses without proportional business value. ## How to detect 5 checks to find it in your estate. - Identify Azure SQL Database instances deployed in the Business Critical service tier - Review associated workload environments to determine if the instance supports production or non-production use - Assess application performance and availability requirements to confirm if Business Critical features are necessary - Evaluate whether General Purpose or Hyperscale tiers would adequately meet workload needs - Validate findings with application owners, development teams, or database administrators before making changes ## How to fix 4 ways to remove the waste. - Migrate non-production SQL instances from the Business Critical tier to a lower-cost alternative, such as General Purpose. - Use downtime windows or database copy strategies to minimize risk during tier transitions, depending on instance size and availability requirements. - Monitor performance after migration to ensure the workload remains stable and meets operational needs. - Update deployment templates and provisioning practices to avoid defaulting non-production instances to the Business Critical tier going forward. ## Documentation Vendor references for pricing and configuration. - [vCore purchasing model - Azure SQL Database learn.microsoft.com](https://learn.microsoft.com/en-us/azure/azure-sql/database/service-tiers-sql-database-vcore?view=azuresql) - [Azure SQL Database pricing azure.microsoft.com](https://azure.microsoft.com/en-us/pricing/details/azure-sql-database/single/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure SQL CER-0031 ### [Unnecessary Use of RA-GRS for Azure SQL Backup Storage](https://www.pointfive.co/efficiency-hub/inefficiencies/unnecessary-use-of-ra-grs-for-azure-sql-backup-storage) Azure SQL databases often use the default backup configuration, which stores backups in RA-GRS storage to ensure geo-redundancy. While suitable for high-availability production systems, this level of resilience may be unnecessary for... Databases - Azure SQL CER-0264 ### [Suboptimal Use of Serverless Compute for Azure SQL Database](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-use-of-serverless-compute-for-azure-sql-database-4fe48) Serverless is attractive for variable or idle workloads, but it can become more expensive than Provisioned compute when database activity is high for long portions of the day. As active time increases, per-second compute accumulation... Databases - Azure SQL CER-0263 ### [Suboptimal Use of Provisioned Compute for Azure SQL Database](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-use-of-provisioned-compute-for-azure-sql-database-9bb83) Databases deployed on Provisioned compute incur continuous hourly charges even when workload demand is low. For databases that are active only briefly within an hour, or for limited hours per month, Serverless can provide significantly... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.