Change the service tier and performance level (pricing tier) of a SQL database using the Azure portal
Service tiers and performance levels describe the features and resources available for your SQL database and can be updated as the needs of your application change. For details, see Service Tiers.
Note that changing the service tier and/or performance level of a database creates a replica of the original database at the new performance level, and then switches connections over to the replica. No data is lost during this process but during the brief moment when we switch over to the replica, connections to the database are disabled, so some transactions in flight may be rolled back. This window varies, but is on average under 4 seconds, and in more than 99% of cases is less than 30 seconds. Very infrequently, especially if there are large numbers of transactions in flight at the moment connections are disabled, this window may be longer.
The duration of the entire scale-up process depends on both the size and service tier of the database before and after the change. For example, a 250 GB database that is changing to, from, or within a Standard service tier, should complete within 6 hours. For a database of the same size that is changing performance levels within the Premium service tier, it should complete within 3 hours.
Use the information in Azure SQL Database Service Tiers and Performance Levels to determine the appropriate service tier and performance level for your Azure SQL Database.
- To downgrade a database, the database should be smaller than the maximum allowed size of the target service tier.
- When upgrading a database with Geo-Replication enabled, you must first upgrade its secondary databases to the desired performance tier before upgrading the primary database.
- When downgrading a service tier, you must first terminate all Geo-Replication relationships.
- The restore service offerings are different for the various service tiers. If you are downgrading you may lose the ability to restore to a point in time, or have a lower backup retention period. For more information, see Azure SQL Database Backup and Restore.
- Changing your database pricing tier does not change the max database size. To change your database max size use Transact-SQL (T-SQL) or PowerShell.
- The new properties for the database are not applied until the changes are complete.
To complete this article you need the following:
- An Azure SQL database. If you do not have a SQL database, create one following the steps in this article: Create your first Azure SQL Database.
Open the SQL Database blade for the database you want to scale up or down:
- In the Azure portal, click More services > SQL databases.
- Click the database you want to change.
On the SQL database blade click Pricing tier (scale DTUs):
Choose a new tier and click Select:
Clicking Select submits a scale request to change the pricing tier. Depending on the size of your database the scale operation can take some time to complete (see the info at the top of this article).
Click the notification icon (bell), in the upper right:
Click the notification text to open the details pane where you can see the status of the request.
- Change your database max size using Transact-SQL (T-SQL) or PowerShell.
- Scale out and in
- Connect and query a SQL database with SSMS
- Export an Azure SQL database