Database migration
Database migration
Database migration is an example of specialized workload migration. Many public and private cloud
providers offer tools that can facilitate or automate parts of the database migration process to ensure
that your database remains secure throughout the transfer and that no data loss or corruption occurs.
Additionally, most cloud providers offer migration services that can verify your data’s integrity after the
transfer.
Typically, the first step in the database migration process involves converting the source database’s
schema (if necessary) so that it’s compatible with the target database. A database’s schema is like a
blueprint for how it is organized, controlling its logical architecture and structure. If the target database
management system uses a data definition language (DDL) that is not compatible with the source’s, the
schema will need to be converted.
The next steps are to migrate the data and set up ongoing incremental data warehouse updates. You can
also consolidate multiple different databases into one during this process, if necessary. To learn more
about how data is organized when stored in the cloud, take a look at “Cloud Databases Explained”.
Migrating an entire data center environment to the cloud or another location is a large-scale,
comprehensive process. Completing such a migration project successfully—with minimal downtime or
disruption to operations—requires careful planning and coordination.
When contemplating a data center migration or any other large-scale data migration project, it’s
important to consider timelines early in the planning stages, since petabyte-scale transfers can take
multiple weeks to complete, even with relatively high-speed network connections.
The more carefully your enterprise plans its data migration, the less likely you are to encounter surprise
costs or unplanned downtime and the less likely it is that your end users will be frustrated or
inconvenienced during and after the migration. You’ll want to establish goals, set a timeline, and
anticipate any challenges that you may encounter.
There are three primary factors you should consider when determining how you’ll approach the project:
Volume of data. When you’re migrating fewer than 10 terabytes (TB) of data, shipping the data to its
new storage location on a client-provided storage device is often the simplest and most cost-effective
method. For transfers involving larger amounts of data—say, up to multiple petabytes (PB)—a
specialized data migration device supplied by your cloud provider can be the most convenient and
affordable option. While, in theory, you could use online migration for any amount of data, time
constraints limit its feasibility for large amounts of data.
Speed to completion. For online migrations, the amount of data being transferred and the speed of your
network connection will determine how long data migration takes. For offline migrations, shipping time
must be taken into account. If start-to-finish migration speed is your primary concern—and if you have
adequate available bandwidth to dedicate to the migration—online transfer could be the best option.
But if your migration deadline is flexible and/or you have bandwidth or other networking constraints,
offline migration might be the right choice.