![]() ![]() ![]() If you’re familiar with setting up replication infrastructure for PostgreSQL, you’re probably good to jump in, and check in on the documentation if needed. I’ll start by saying, the documentation and in-product UI guidance are both excellent for DMS. Today, I want to take a moment with you to cover preparing your source PostgreSQL instance and database(s) for migration using DMS and some gotchas I found so you don’t have to. Network topology can be incredibly complicated, and connecting two machines securely through the internet while serving an application with thousands or millions of users is anything but simple. I wrote a thorough blog post walking through the various connectivity options for DMS in great detail. Not to downplay the difficulty in database prep, or connectivity. When it's all finished, cutting over to using your Cloud SQL instance as your application's primary database is as simple as clicking a button in the DMS UI. Once you get your source instance and database(s) prepared, and establish the connectivity between source and destination, doing the migration is all handled. The thing I’ve appreciated the most about diving deep with DMS has been that it just works. Today, we’ve officially made the product generally available, and bring the same easy-to-use migration functionality to PostgreSQL. Last November, we made relational database migration easier for MySQL users with our public preview of Database Migration Service (DMS). ![]()
0 Comments
Leave a Reply. |