Nesta página, confirma que a tarefa de migração migrou corretamente os dados da instância da base de dados de origem para a instância da base de dados do Cloud SQL de destino.
No mínimo, verifique se a instância da base de dados e as respetivas tabelas existem na instância do Cloud SQL. Também pode validar a quantidade de linhas ou o conteúdo exato das tabelas.
Execute comandos SQL para validar a migração. Por exemplo:
No comando postgres, introduza \list para listar as bases de dados e verifique se vê a instância da base de dados de origem.
No comando postgres, introduza \connect SOURCE_DB_NAME e introduza a palavra-passe quando lhe for pedido para se ligar à instância da base de dados e ver as tabelas associadas à instância. O nome do comando muda de postgres para SOURCE_DB_NAME.
No comando SOURCE_DB_NAME, introduza \dt para ver as tabelas desta instância.
No comando SOURCE_DB_NAME, introduza GRANT cloudsqlexternalsync to USER; porque quer conceder a este utilizador autorização para aceder aos dados nas tabelas desta instância. Além disso, substitua USER pelo nome do utilizador que usou para estabelecer ligação à instância da base de dados de destino.
No comando SOURCE_DB_NAME, introduza SELECT * from TABLE_NAME; para ver as informações replicadas de uma tabela na instância da base de dados de origem.
Confirme que vê as informações corretas na tabela.
Verifique se as restrições, como chaves principais, chaves externas e índices, foram migradas corretamente para a instância da base de dados do Cloud SQL de destino.
Se tudo o que verificar estiver como esperado, significa que o Database Migration Service migrou os dados corretamente.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-21 UTC."],[[["\u003cp\u003eThis guide helps verify that a database migration job has correctly transferred data from a source database to a destination Cloud SQL instance.\u003c/p\u003e\n"],["\u003cp\u003eThe basic verification process includes confirming the existence of the migrated database instance and its tables in the Cloud SQL instance.\u003c/p\u003e\n"],["\u003cp\u003eYou can also run SQL commands through the Cloud Shell to check the row counts or exact contents of migrated tables.\u003c/p\u003e\n"],["\u003cp\u003eTo check data integrity, one must grant specific user permissions to access table data via the cloud shell.\u003c/p\u003e\n"],["\u003cp\u003eChecking constraints such as primary keys, foreign keys, and indexes should also be verified in the destination database.\u003c/p\u003e\n"]]],[],null,["# Verify a migration\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n[MySQL](/database-migration/docs/mysql/verify-migration \"View this page for the MySQL version of Database Migration Service.\") \\| PostgreSQL \\| [PostgreSQL to AlloyDB](/database-migration/docs/postgresql-to-alloydb/verify-migration \"View this page for the PostgreSQL to AlloyDB version of Database Migration Service.\")\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nVerifying a migration\n---------------------\n\nIn this page, you confirm that the migration job migrated data from your source database instance to the destination Cloud SQL database instance correctly.\n\n\u003cbr /\u003e\n\nAt a minimum, verify that the database instance and its tables exist in the\nCloud SQL instance. You can also verify the tables' row counts or exact\ncontents.\n\n\nThe following steps show a minimal example:\n\n1. Go to the [SQL Instances page](https://console.cloud.google.com/sql) in the Google Cloud console.\n2. Click the read replica entry of your migration job.\n3. Click the **Activate Cloud Shell** icon that appears in the upper-right region of the page.\n4. At the Cloud Shell prompt, press **Enter**.\n5. Optional: If an **Authorize Cloud Shell** dialog box appears, then click **Authorize**.\n6. At the **Enter password** prompt, enter the password that you either provided or that Database Migration Service generated for you in [Define and create the destination Cloud SQL instance](/database-migration/docs/mysql/create-migration-job#dest).\n7. Run SQL commands to verify the migration. For example:\n 1. At the **postgres** prompt, enter `\\list` to list the databases and verify that you see your source database instance.\n 2. At the **postgres** prompt, enter `\\connect `\u003cvar translate=\"no\"\u003eSOURCE_DB_NAME\u003c/var\u003e, and enter the password when prompted, to connect to the database instance and see the tables associated with the instance. The name of the prompt changes from `postgres` to \u003cvar translate=\"no\"\u003eSOURCE_DB_NAME\u003c/var\u003e.\n 3. At the \u003cvar translate=\"no\"\u003eSOURCE_DB_NAME\u003c/var\u003e prompt, enter `\\dt` to see the tables of this instance.\n 4. At the \u003cvar translate=\"no\"\u003eSOURCE_DB_NAME\u003c/var\u003e prompt, enter `GRANT cloudsqlexternalsync to `\u003cvar translate=\"no\"\u003eUSER\u003c/var\u003e`;` because you want to give this user permission to access the data in the tables of this instance. Also, replace \u003cvar translate=\"no\"\u003eUSER\u003c/var\u003e with the name of the user you used to connect to the destination database instance.\n 5. At the \u003cvar translate=\"no\"\u003eSOURCE_DB_NAME\u003c/var\u003e prompt, enter `SELECT * from `\u003cvar translate=\"no\"\u003eTABLE_NAME\u003c/var\u003e`;` to see the information that's replicated from a table in your source database instance.\n 6. Verify that you see the correct information in the table.\n8. Verify that constraints such as primary keys, foreign keys, and indexes were migrated to the destination Cloud SQL database instance correctly.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nIf everything you check is as you expect, then Database Migration Service has migrated the data correctly."]]
