Logging Stay organized with collections Save and categorize content based on your preferences.
Database Migration Service uses Cloud Logging. You can access two log categories toacquire detailed information on events that occur with relation to your migrationjobs: Database Migration Service logs, and the destination Cloud SQL for PostgreSQL logs.
Database Migration Service logs
Database Migration Service for SQL Server to Cloud SQL for PostgreSQL providesstructured logs for thedatamigration.googleapis.com/MigrationJob,datamigration.googleapis.com/ConnectionProfile,anddatamigration.googleapis.com/PrivateConnectionresources.These logs represent real-world events, such as when a migration job is created,when Database Migration Service reads information from your source database,or when a connection profile is edited.
Each log entry contains ajsonPayload.textMessage field with a description tohelp you better understand the event. There are different types of messages,for example:
Sample log messages for thedatamigration.googleapis.com/MigrationJob resource | |
|---|---|
| Log text message | Description |
FULL DUMP read is completed for table: {SCHEMA_TABLE_NAME} | This message means that Database Migration Service finished reading specific table data in your source database for the full dump phase. This message indicates that the full dump phase for the table is in an advanced stage and is likely to complete shortly. |
Successfully loaded {NUMBER} FULL DUMP rows into table: {SCHEMA_TABLE_NAME} | This message means that Database Migration Service finished writing a batch of rows into a specific table in your destination instance during the full dump phase. |
Successfully applied {NUMBER} CDC rows into table: {SCHEMA_TABLE_NAME} | This message means that Database Migration Service finished writing a batch of rows into a specific table in your destination instance during the CDC phase. |
Accessing data of table: {SCHEMA_TABLE_NAME} for data processing purpose | When you use a CMEK for your migration job, this message indicates that Database Migration Service accessed the encryption key to process data for a specific table. |
Cloud SQL for PostgreSQL instance logs
Cloud SQL for PostgreSQL also provides log entries for your destination instance.See theCloud SQL logs reference in the Cloud Logging documentation.
View and query logs
To view your logs, perform the following:
- In the Google Cloud console, go to theMigration jobs page.
- In theJobs tab, click the display name of the migration job for which you want to view logs.
The migration job details page opens.
- On the migration job details page, clickView logs and perform one of the following:
- To view migration job logs, selectMigration job logs.
- To view logs for your Cloud SQL for PostgreSQL destination instance, selectDestination instance logs.
TheLogs Explorer page opens.
- On theLogs Explorer page, you can use the drop-down menus to modify the query and filter log entries. For example, to filter migration job logs for events where Database Migration Service accessed a specific table in your source database, you can use a query similar to the following:
resource.type="datamigration.googleapis.com/MigrationJob"resource.labels.migration_job_id="MIGRATION_JOB_ID"jsonPayload.textMessage:"Accessing data of table"
What's next
For more information on using Logs Explorer, seeView logs by using Logs Explorer.
For a detailed reference of what fields are supported in Database Migration Servicelog entries, seeDatabase Migration Service logs reference.
To get a complete, step-by-step migration walkthrough, seeSQL Server to Cloud SQL for PostgreSQL migration guide.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-19 UTC.