Scribd
Upload
1 views3 pages

Database Migrations

Uploaded by

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

Database Migrations

Uploaded by

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

Migration Strategy - Factors to consider

- Assess whether we are going with the same database or a different database
- If the migration is to the same database - We can simply follow a
Lift and Shift approach
- Unless we want to move to open source database systems to save costs
- If the migration is to a different database - We need to choose
proper Migration Tools and Schema Conversion Tools and an intermediate replication
instance for migration process.
- Assess and decide on whether we need to perform an Offline or an Online
migration

- Assess the Disater Recovery requirements


Recovery Time
How much data loss is acceptable? based on business requirements

- Backup Strategy
Weekly Full Backups
Daily Differental Backups
Hourly Incremental Backups

- High Availability
by Clustering

DB migration, in general

- Analyze the existing database


- Choose one of the migration tools (Ora2Pg, pgloader, AWS DMS and OpenDBCopy)
- Configure the migration tool
- Convert the schema
- Migrate the data
- Test the migrated data
- Switch to the new database

===============================
1. On-Prem to Cloud Migration - Oracle to Amazon RDS

Migration from Oracle to Amazon RDS


- I have created an Oracle database instance in Amazon RDS
- master user credentials
- DB instance size (Standard, Memory Optimized and Burstable)
- Storage (General Purpose, Provisioned IOPS)
- Availability - Multi-AZ
- VPC, Subnet and Security Group
- Next up, I have created a replication instance in AWS DMS
- Later, I have created endpoints in AWS DMS
- Next up, I have created a replication task in AWS DMS
- Later, I have completed the migration and cleaned up resources

===============================
2. On-Prem to Cloud Migration - SQL Server to Amazon RDS

Migration from SQL Server to Amazon RDS


- I have created a SQL Server database instance in Amazon RDS
- Next up, I have created a replication instance in AWS DMS
- Later, I have created source and target endpoints for your database
migration
- Next up, I have created a replication task in AWS DMS
- Later, I have completed the migration and cleaned up resources
==============================
Database Migration from Oracle to Postgres
==
In order to implement a successful database migration, one should have, a well
defined migration strategy and a well laid migration plan.

And as a part of that, during my experience of, migrating from Oracle to Postgres,

- I checked for the size of the database, quality of the data, and the sensitivity
of the data, and any regulatory requirements around it.

- I also performed the analysis of the existing Oracle database and identified all
the objects that need to be migrated, such as tables, views, stored procedures,
functions, triggers, etc.

- I then chose Ora2Pg as the migration tool for migrating Oracle databases to
Postgres and configured it by providing the necessary credentials and connection
details for both the Oracle and Postgres databases.

- I then converted the Oracle schema to a Postgres-compatible schema. This involved


translating Oracle data types, constraints, and other database objects to their
Postgres equivalents.

- I then migrated the data from the Oracle database to the Postgres database. This
was done using bulk inserts, SQL scripts, and the data replication.

- Once the data was migrated, I performed the testing to ensure that the data has
been migrated accurately and that the application was working correctly. ???

- Once you testing is done, switch the application to use the Postgres database.

====================================
Database Migration from MySQL to Postgres
==
In order to implement a successful database migration, one should have, a well
defined migration strategy and a well laid migration plan.

And as a part of that, during my experience of, migrating from Oracle to Postgres,

- I checked for the size of the database, quality of the data, and the sensitivity
of the data, and any regulatory requirements around it.

- I also performed the analysis of the existing MySQL database and identified all
the objects that need to be migrated, such as tables, views, stored procedures,
functions, triggers, etc.

- I then chose pgLoader as the migration tool for migrating MySQL databases to
Postgres and configured it by providing the necessary credentials and connection
details for both the MySQL and Postgres databases.

- I then converted the MySQL schema to a Postgres-compatible schema. This involved


translating MySQL data types, constraints, and other database objects to their
Postgres equivalents.

- I then migrated the data from the MySQL database to the Postgres database. This
was done using bulk inserts, SQL scripts, and data replication.

- Once the data was migrated, I performed the testing to ensure that the data has
been migrated accurately and that the application was working correctly.

- Once you testing is done, switch the application to use the Postgres database.

You might also like