{"id":10380,"date":"2021-07-16T16:43:12","date_gmt":"2021-07-16T21:43:12","guid":{"rendered":"https:\/\/threecloud.wpengine.com\/post\/moving-azure-sql-database-from-one-subscription-to-another\/"},"modified":"2022-11-30T09:23:51","modified_gmt":"2022-11-30T15:23:51","slug":"moving-azure-sql-database-from-one-subscription-to-another","status":"publish","type":"post","link":"https:\/\/3cloudsolutions.com\/resources\/moving-azure-sql-database-from-one-subscription-to-another\/","title":{"rendered":"Moving Azure SQL Database from One Subscription to Another"},"content":{"rendered":"

Multiple Environments<\/strong><\/h3>\n

Many companies like to separate Production from Development \/ UAT environments. I have frequently seen Dev \/ UAT deployed to one subscription, and Production to a different subscription. This works well for the Finance team because the billing for each environment is separated. However, having the environments in different subscriptions inserts a speed bump in a common practice among DBAs \u2013 restoring a copy of the Production database in the UAT and Dev environments to ensure that code is synchronized across all environments.<\/p>\n

Azure SQL Database Restore Database\u00a0<\/strong><\/h3>\n

\"\"<\/p>\n

In Azure SQL Database, when you select \u201cRestore\u201d, your options are limited to restoring the same server. Notice that the options for changing the subscription, resource group, and server are greyed out. Only the database name can be changed.<\/p>\n

\"\"<\/p>\n

If you need to restore a copy of your Azure SQL database on the same server so that you can copy a deleted table back into your database, then this works fine.<\/p>\n

The restore Azure SQL database operation will not allow restoring the database over the existing database, however, you can change the name of the database at any time.<\/p>\n

 <\/p>\n

Rename Azure SQL Database<\/strong><\/h3>\n

In SQL Server Management Studio run the following command on your Azure SQL Server:<\/p>\n

ALTER DATABASE OriginalDatabaseName MODIFY NAME = NewDatabaseName;<\/p>\n

 <\/p>\n

Azure SQL Database Copy Database<\/strong><\/h3>\n

\"\"<\/p>\n

The next option would be to COPY the database. This option looks promising because it allows the database to be copied to another server, and if a different Azure SQL server does not exist, a new one may be created without having to leave the Copy dialog and create one separately.<\/p>\n

\"\"<\/p>\n

Although the New Server option looks promising, it does not provide the desired options: changing the subscription and resource group.<\/p>\n

\"\"<\/p>\n

All is not lost, a solution exists: since an Azure SQL Server can move from one Subscription to another, the database can be copied to a Migration server, moved to the other Subscription then copied onto the existing server to refresh the existing database.<\/p>\n

It\u2019s Easier than It Sounds<\/strong><\/h3>\n

You must have at least Contributor rights in both subscriptions to successfully perform this operation.<\/p>\n