Navicat Blog

October 3, 2017 by Gavin

Being a MySQL compatible relational database engine, Amazon Aurora amalgamates safety, availability and speed of top notch commercial databases with the easiness and cost efficiency of open source database. The engine has been tagged at 1/10th of the price of the commercial engines.

After determining that Aurora is the database to be used for application development, the second stage is to choose on a migration methodology and to generate a database migration program.

Migration Factors: Source Database

There are two types of migration factors:

  • Homogenous migrations - Percona, MariaDB and MySQL to Amazon Aurora
  • Heterogeneous migrations - Oracle, PostgresSQL, Microsoft SQL Server to Amazon Aurora

Homogeneous Migration

For the source database you desire to migrate is amenable to MySQL 5.6 such as Percona or MariaDB, then you have the below stated migration methodologies:

RDS Snapshot migration: for those who have AWS RDS system accessing their MYSQL Data Base server, then they just have to migrate the database snapshot to the AWS Aurora Database. For downtime migrations, you may either have to terminate your application or may just terminate writing to the database whilst migration and snapshot is in evolvement.

Migration with the help of native Navicat Tools: one can make use of native Navicat tools to migrate the plan from your DB server to AWS Aurora DB. With the help of this approach, you get more control over the database migration procedure.

Migration by utilizing AWS DMS: it is equipment rendered by AWS just to migrate he database scheme to AWS Aurora DB. Before making use of AWS DMS to shift the data, one needs to copy the database plan from the resource to the place where you have targeted via using native Navicat tools.

Making use of AWS DMS is a reliable idea when you do not have the experience to use native Navicat tools. It is provided with the option of having downtime as well as not having downtime methodology.

Heterogeneous Migrations

When the source database you wish to migrate isn’t MySQL compliant database such as PostgresSQL, Oracle to AWS Aurora DB, then you have a number of options accessible to fulfill the migration procedure.

Schema Migration: schema migration to Amazon Aurora from a non-MySQL compliant database can be accomplished by making use of AWS Schema Conversion Tool. It is a desktop app which assists you to convert your database plan from PostgreSQL, Microsoft SQL Server as well as Oracle database to an Amazon RDS MySQL DB or Amazon Aurora DB cluster.

Data Migration: whilst assisting homogeneous migrations with zero downtime, AWS DMS (AWS Database Migration Service) assists constant replication over heterogeneous databases and is a priority alternative to move your resource database to your destination database, for migrations with downtime as well as migrations with near-zero downtime.

With the help of these migrations, you can effectively migrate database to Amazon Aurora. They are the simplest and easiest way to migrate database. So, choose any according to your compliance and then go for it.

Navicat Blogs
Feed Entries
Share
Blog Archives