Scribd
Upload
60 views3 pages

Support in Planning DB Migration

1. Planning a database migration involves understanding the source database, assessing the data quality, and converting the database schema as needed. 2. Common reasons for database migration include upgrading software, moving to lower cost cloud databases, and merging multiple databases. 3. Key steps in planning a migration are understanding the source database, assessing data quality, converting the schema, testing migration builds, and executing the full migration. Follow-up may involve coordinating teams and escalating any issues.

Uploaded by

Vijay Rajendiran
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
60 views3 pages

Support in Planning DB Migration

1. Planning a database migration involves understanding the source database, assessing the data quality, and converting the database schema as needed. 2. Common reasons for database migration include upgrading software, moving to lower cost cloud databases, and merging multiple databases. 3. Key steps in planning a migration are understanding the source database, assessing data quality, converting the schema, testing migration builds, and executing the full migration. Follow-up may involve coordinating teams and escalating any issues.

Uploaded by

Vijay Rajendiran
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Support in planning DB Migration

Description:
DB migration is moving data from one or more source platforms to another target database.
There are several reasons for migrating from one database to another. For example, a
business might want to save resources by switching to a cloud-based database.

Pre-requisites:
1. Need to know Client’s requirement
2. Migration Strategy

Why Use Database Migration?

The common reasons for using database migration are:

 Upgrading to the latest version of the database software to improve security and
compliance
 Moving existing data to a new database to reduce cost, improve performance, and
achieve scalability
 Moving from an on-premise database to a cloud-based database for better scalability
and lower costs
 Merge data from several databases into a single database for a unified data view
post-merger.

Steps in Planning and supporting DB Migration:

1. Understanding the Source Database

A vital database migration step to understand is the source data that will populate your
target database before starting any database migration project. Here are the questions that
you should be able to answer about your source database:

 What is the size of the source database? The size and complexity of the database
you are trying to migrate will determine the scope of your migration project. This will
also determine the time and computing resources required to transfer the data.
 Does the database contain ‘large’ tables?’ If your source database contains tables
that have millions of rows, you might want to use a tool with the capability to load
data in parallel.
 What kind of data types will be involved? If you migrate data between different
databases, such as an SQL database to an Oracle one, you will need schema
conversion capabilities to successfully execute your DB migration project.

2. Assessing the Data

This step involves a more granular assessment of the data you want to migrate. You would
like to profile your source data and define data quality rules to remove inconsistencies,
duplicate values, or incorrect information.

Data profiling at an early stage of migration will help you mitigate the risk of delays, budget
overruns, and even complete failures. You will also be able to define data quality rules to
validate your data and improve its quality and accuracy, resulting in efficient DB migration.

3. Converting Database Schema

Heterogeneous migrations involving migration between different database engines are


relatively more complex than homogenous migrations.

While schemas for heterogeneous database migrations can be converted manually, it is


often very resource-intensive and time-consuming.

Therefore, using a data migration tool with database schema migration conversion


capability can help expedite the process and migrate data to the new database.

4. Testing the Migration Build

It’s a good idea to adopt an iterative approach to testing a migration build.

You can start with a small subset of your data, profile it, and convert its schema instead of
running a full migration exercise at once. This will help you ensure that all mappings,
transformations, and data quality rules are working as intended.

Once you have tested a subset on your database migration tool, you can increase the data
volume gradually and build a single workflow.

5. Executing the Migration

It is more important than ever before to plan DB migrations to minimize or outright


eliminate interruptions to everyday data management processes.

This can be achieved with paid and free database migration tools that offer data
synchronization or Change Data Capture (CDC) functionality.

Using these tools, you can perform the initial load and then capture any changes during or
after the initial load.
Once all the data has been migrated to the new database successfully, a retirement policy
needs to be developed for the old database, if required.

In addition, systems need to be put into place to validate and monitor the quality of the
data transferred to the target database.

Email-Follow-up:

1. We can co-ordinate with the team while migrating database and will ensure all the
above mentioned follows.

2. If any challenges in configuring migration services, we can approach MS support.

3. If the challenge is related to the internal network, then we can approach NHC team.

4. For the quick redressal of migration issue we can ask MS for fast-track engineer as
well to support on this.

5. Based on Client requirement we can migrate database periodically.

You might also like