Azure SQL Database
An Azure relational database service.
5,662 questions
Below MSFT documentation serves as the guide for cloning of database across diff tenant.
and the performance aspects
How to migrate some databases sources from a directory active to another
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 18%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELA%3C/text%3E%3C/svg%3E)
Laura Alvarez
20
Reputation points
I need to migrate two SQL databases from a subscription located in one Azure Active Directory (tenant) to another directory (tenant). The databases are live, receiving incoming data. I initially attempted to use Azure Database Migration Service (DMS) and Azure Data Factory, but they have limitations when it comes to migrating between different tenants.
I am seeking confirmation on which service is best suited for handling this cross-tenant migration while maintaining application availability and data integrity during the process. Managing downtime and ensuring continuous data synchronization is critical due to the active nature of the databases.
{count} votes
-
Nandan Hegde 32,256 Reputation points MVP2024-09-05T15:39:51.2966667+00:00 How is your application currently authenticating to the database? Because my guess is there is bound to be some down time due to change in tenant which in turn would lead to change in some authentication method/values
-
Laura Alvarez 20 Reputation points
2024-09-05T16:18:15.5466667+00:00 You’re absolutely right. The change in tenant will likely lead to a modification in some authentication methods or values (connection string and authentication method), which could cause downtime. However, the key focus here is determining the right service or approach that can help minimize that downtime and potentially automate the process. By choosing the right migration strategy—such as using automated data synchronization or a Azure service that supports the migration between different directories seamless cutover—we can mitigate the impact on the application's availability.
Sign in to comment
Accepted answer
1 additional answer
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 83%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENJ%3C/text%3E%3C/svg%3E)
Neuvi Jiang 1,300 Reputation points Microsoft Vendor2024-09-06T02:35:51.2833333+00:00 Hi Laura Alvarez,
Thank you for posting in the Microsoft Community Forums.
- Evaluate existing tools and services
Azure Database Migration Service (DMS): While DMS is a powerful tool that supports a wide range of database migration scenarios, it does suffer from the limitations of inter-tenant migrations.DMS is primarily designed for migrations within the same tenant, and therefore may not be the best choice for cross-tenant migrations.
Azure Data Factory (ADF): ADF is primarily used for data integration and ETL operations, and while it supports cross-tenant data movement, it may not be specifically designed for database migration, especially in scenarios where database integrity and real-time performance need to be maintained.
- Recommended migration strategies
Use TSQL to replicate the database:
By writing TSQL scripts, you can replicate databases across tenants to servers under different subscriptions or resource groups. This approach is flexible, supports cross-subscription migration, requires no additional tools, but requires additional privilege configuration and SQL authentication.
Benefits: Flexible, supports cross-subscription migration, no additional tools required.
Limitations: Requires additional permissions configuration and SQL authentication.
Use Database Backup and Restore:
Back up the database as a BACPAC file, then upload it to Azure Storage and restore it in the target tenant. This method is suitable for small-scale database backups and migrations.
Benefits: Easy to use, suitable for any SQL Database recovery.
Limitations: Export is limited to a single database, not suitable for large-scale data volume databases or synchronized multi-database migration.
Transaction Replication:
Transactional replication is a method of moving data between continuously connected database servers, ideal for online or offline migration of large and complex databases.
Benefit: Supports real-time data synchronization for large and complex databases.
Limitations: Relatively complex configuration, need to ensure that the network connection between the source and target database is stable.
- Maintain application availability and data integrity
Minimize downtime: If possible, try to migrate during low business peak hours to minimize the impact on applications.
Data synchronization: Ensure data synchronization between the source and target databases during the migration process. If transactional replication is used, make sure there are no delays or errors in the replication process.
Rollback plan: Develop a detailed rollback plan so that you can quickly revert to the original state if problems occur during the migration.
Testing: Before migration, simulate the migration process in a test environment to ensure that everything works as expected.
- Additional Considerations
Security: Ensure that all relevant security best practices are adhered to during the migration process, including data encryption and access control.
Compliance: Ensure that the migration process meets all applicable legal and regulatory requirements.
In summary, for the need to migrate live SQL databases across tenants and maintain application availability and data integrity, a TSQL replicated database or transactional replication approach is recommended. These approaches offer flexibility and the ability to synchronize real-time data, but also require careful planning and execution to ensure success.
Best regards
Neuvi