Hey everyone! I'm trying to get a grasp on migrating an on-premises SQL database to Azure but I've never done this before. I've done a bit of research and talked to ChatGPT, and here's what I've put together so far:
1. **Define the Migration Strategy**: I'm considering the BACPAC method for smaller databases (50–100 GB) if I can manage some downtime, or using the Database Migration Service (DMS) for larger databases (300-500 GB or more) where I want to minimize downtime.
2. **Pre-Requisite Tasks on On-Prem Database**: I know I need to check the database health using DBCC CHECKDB, run a DMA Assessment to find unsupported features, verify against size considerations for BACPAC, clean up any unused data, capture performance baselines, and ensure I have a backup before starting.
3. **Perform Migration**: I plan to execute the migration using either BACPAC or DMS, migrating the schema first and then the data.
4. **Post-Migration Validation**: After the migration, I want to validate data consistency and check the performance compared to my baseline.
Are these steps correct, or am I missing anything? Any suggestions would be greatly appreciated!
3 Answers
Just a heads-up, migrating to Azure SQL DB does have some significant differences compared to on-prem. Azure SQL doesn’t support features like SQL Agent or cross-database queries, so check your app compatibility first. If you're moving to a managed instance or a VM instead, that could be easier due to backup and restore options, but you’ll have to look into potential downtime since Azure SQL’s import/export method can fail. It's also worth noting that DMS essentially utilizes BACPAC, so ensure you're prepared for that process, especially for anything over 50GB. Overall, proceed with caution!
I've migrated a SQL Server database to Azure before and found the Azure migration tool to be super user-friendly for my 30GB database. If you just want a straightforward move, it handles most of what you've outlined. So, you're definitely on the right track!
Thanks for the advice!
The DMA tool is excellent for checking compatibility and copying schemas. Keep it handy for a quick schema assessment. If you're working with huge data sets, like 10TB, and time is of the essence, DMS is essential, but you'll need strong integration runtimes to handle the transfer efficiently. If your databases are small, you could get away with DMA on the weekend without much hassle. BACPAC works for smaller DBs too, but it's a bit of a setup for storage and import.
Good advice! Just be sure to start your post with more context about your setup; it will help others give you better answers!