Heterogeneous DB Migrations Decision Tree — Cloud SQL & Spanner
This is the second in series for the decision tree for heterogeneous DB migrations to Google cloud. We see a lot of traction for db migrations with relational databases like Cloud SQL and cloud native databases i.e. Cloud Spanner.
Especially for heterogeneous database migrations i.e. cross database engines there is a lot of due diligence needs to be done.
Step 1 — Discovery of DB landscape on data estate with tools of choice. At Google cloud the widely used tool is Stratozone or feel free to use any other tool of your choice.
Step 2- DB Migration Assessment with our partner tool i.e. migVisor (our GCP partner tool from EPAM)
Step 3 — Source database schema conversion to make it compatible with target databases. For example — let’s say you are migrating from Oracle to Postgres(Cloud SQL) a widely used tool you can prefer is Ora2pg or a tool from our partner Striim which has capability for schema conversion.
Step 4 — Then ideally the step is for code conversion. Again at Google Cloud we have strong partner ecosystem i.e. Ispirer or recent acquisition from Google cloud with Compiler Works.
Step 5 — Then data movement or data migration from source to target. This includes both initial snapshot of source database and incremental changes on the source database to target with CDC features. Depending on the use case Google Database Migration Service or our Partner tools like Striim etc.
Step 6 — Data Validations on the target once the data is moved. Pls check this very handy tool DVT
Of Course lets not forget rollback strategy
In this blog we will discover the path from Oracle DB to Postgres and path to Cloud Spanner.
Stay tuned for an upcoming blog on DB Migration !!!!
