Select a new tier for each Web or Business database. You can always browse the available pricing tiers and select the one that suits your environment best.Īfter clicking the suggested tier you will be presented with the Choose your pricing tier blade where you can select a tier and then click the Select button to change to that tier. In the Upgrade this server blade select each database to review and select the recommended pricing tier to upgrade to. The service recommends the best tier for running your existing database’s workload by analyzing the historical usage for your database. To assist you with upgrading, the SQL Database service recommends an appropriate service tier and performance level (pricing tier) for each database. During the process of upgrading to SQL Database V12 you will update all Web and Business databases to a new service tier. If your server has any Web or Business databases you must upgrade them. Select Latest SQL database update, then select Upgrade this server. In the Azure Portal browse to the server you want to upgrade by selecting BROWSE ALL > SQL servers, and selecting the desired server. For details, see Ports for SQL Database V12. Open these ports if you have clients on an Azure VM: If your client program connects to SQL Database V12 while your client runs on an Azure virtual machine (VM), you must open port ranges 11000-1190-14999 on the VM.After the upgrade completes reconfigure your database for geo-replication. ![]() Review and suspend geo-replication: If your Azure SQL database is configured for geo-replication you should document its current configuration and stop geo-replication.Upgrade all Web and Business databases: See Upgrade all Web and Business databases section below or use PowerShell to upgrade databases and server.V11 server recommendation history does not apply to V12 servers so it is not retained. After an upgrade the server cannot be reverted to V11.Īfter upgrading to V12, service tier recommendations and elastic pool recommendations will not immediately be available until the service has time to evaluate your workloads on the new server. Upgrading to SQL Database V12 cannot be undone. If your application has transient fault handling for connection terminations then it is sufficient to protect against dropped connections at the end of the upgrade. At the time of the actual transition to the new performance level temporary dropping of the connections to the database can happen for a very small duration that is typically around 90 seconds but can be as much as 5 minutes. Note that your databases will remain online and continue to work throughout the upgrade operation. Directions are provided later in this article to create the pool after the server upgrade if you have databases that can benefit from a pool. You can also use the portal to migrate V11 databases into a pool but in the portal you must already have a V12 server to create a pool. You can easily auto-migrate databases from V11 servers directly into elastic database pools using PowerShell. If you have databases on multiple servers consider moving them into the same server and taking advantage of putting them into a pool. Pools also simplify database management because you only need to manage the performance settings for the pool rather than separately managing the performance levels of individual databases. In addition, migrating to an elastic database pool can be more cost effective than upgrading to individual performance levels (pricing tiers) for single databases. This article provides directions for upgrading existing SQL Database V11 servers and databases to SQL Database V12.ĭuring the process of upgrading to V12 you will upgrade any Web and Business databases to a new service tier so directions for upgrading Web and Business databases are included. Improved premium performance and new performance levels.Increased compatibility with SQL Server. ![]() SQL Database V12 has many advantages over the previous version including: SQL Database V12 is the latest version so upgrading to SQL Database V12 is recommended. ![]() Upgrade to Azure SQL Database V12 using the Azure Portal
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |