Files
azuredatastudio/extensions/azurehybridtoolkit/notebooks/hybridbook/content/offline-migration
Christopher C cb8c4b80d0 wording, removing ref to "bootstrap" (#15187)
* wording, removing ref to "bootstrap"

* removing configure-ag nb; unfinished
2021-07-23 16:58:43 -07:00
..
2021-01-25 17:31:43 -08:00
2021-02-23 13:36:09 -08:00
2021-01-25 17:31:43 -08:00

Offline Migration

Home

This chapter is useful for performing an Offline Migration of SQL Server 2005 and above to Azure using ADS Notebooks. Offline migrations are by definition disruptive to the flow of data such as in a web application. With these notebooks, a foundation for automated offline migration can be built.

There are many methods to consider when migrating to the cloud. The notebooks in this chapter cover the following scenarios:

Notebooks in this Chapter

Why Migrate Data Offline?

There are many reasons to do an offline data migration. If the cost of losing connectivity for the duration of an offline migration can be minimized, then it often outperforms ensuring uptime when moving to the cloud from on-premise. Consider the time it takes to develop and test the deployment process, the infrastructure required to switch networking routing dynamically, and the cost of managing a migration team with the appropriate skills required for an online migration.

Recommendations for a Successful Migration

Since the Data Migration Assistant and the Data Migration Service both complement a full migration, use the Assessments notebooks and fix all recommendations prior to migration to avoid potential problems during and after migration.

  • All pre-requisite libraries are outlined in the pre-requisites notebook
  • Always keep backups of the data in standard formats available to be redeployed in case of a problem
  • Test the entire migration process including the process used to restore from backup
  • Automate the migration in such a way that anyone can perform it, given access
  • Consider creating a new notebook that contains simple data tests with known values on the new system after deployment