Stay organized with collections
Save and categorize content based on your preferences.
From a networking point of view, Database Migration Service and AlloyDB for PostgreSQL are
service producers that reside in their own dedicated networks
(known as service networks), outside the Virtual Private Cloud (VPC)
networks that you use in your Google Cloud project.
The goal of configuring network connectivity for a migration process is to
ensure that Database Migration Service can reach your source
SQL Server database and the destination AlloyDB for PostgreSQL
cluster.
Before you configure the source or destination databases, we recommend
that you consider what networking methods you can use to establish the
necessary network connections. See the following pages:
Networking overview describes the high-level, end-to-end
migration networking landscape.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-12 UTC."],[[["This feature facilitates heterogeneous migrations from SQL Server to AlloyDB for PostgreSQL using Database Migration Service."],["Database Migration Service and AlloyDB reside in separate service networks, distinct from your Google Cloud project's VPC."],["Configuring network connectivity is crucial to enable Database Migration Service to access both the source SQL Server database and the destination AlloyDB cluster."],["Detailed guidance on the networking aspects of the migration, including source and destination methods, is available in separate documents."],["A complete step-by-step guide is available to assist users through the migration from SQL Server to AlloyDB for PostgreSQL."]]],[]]
