How To Resize Azure SQL Database

Overview

When the number of users and devices for your app increases from a small number to millions, Azure SQL Database and SQL Managed Instance automatically scale with little downtime. One of the most crucial features of platform as a service (PaaS) is scalability, which allows you to dynamically add extra resources to your service as needed. You may quickly modify the resources (CPU power, memory, IO throughput, and storage) allotted to your databases with Azure SQL Database.

You won't have to worry about purchasing hardware or updating the underlying infrastructure. Using a slider on the Azure portal, scaling a database is simple.

While Azure SQL Managed Instance only supports the vCore-based pricing model, Azure SQL Database offers both the DTU-based and vCore-based purchasing models.

• To handle light to heavyweight database workloads, the DTU-based pricing model provides a combination of compute, memory, and I/O resources in three service tiers: Basic, Standard, and Premium. You can mix and match these resources according to performance levels inside each tier, and you can also add more storage resources to the mix.
• You can select the number of vCores, the quantity of memory, and the speed of storage using the vCore-based pricing model. General Purpose, Business Critical, and Hyperscale are the three service categories available under this purchasing strategy.

Step 1

Open the Overview page of the replica database and the SQL Databases module in Azure to resize the database. Take note of the "Resource Group" and "Location." The location will not be the same as the primary DB. The name of the resource group for the backup database will finish in "asr," which stands for Azure Site Recovery. Keep in mind that the "Pricing Tier" will be modified now, however it will initially match the primary DB.

Step 2

Under "Settings," choose the "Compute and Storage" blade. Slider should be all the way to the left, to "10 DTUs," or S0. The following caution is visible above the slider control. Take note: The primary and secondary databases should have the same computational size, it is strongly advised. In contrast to this message, we discussed this issue with Microsoft and came to the conclusion that the sizes of the primary and secondary databases did not need to match. The database size would need to be increased in the event of a failover (secondary DB promoted to primary) in order to accommodate the processing requirements of the customer's production system. To change the database's size, click the Apply button.

Summary

In this article, we covered How to Resize the Azure SQL Database. If you have any questions, kindly post a comment in the comment section.