Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini menjelaskan cara mengonfirmasi bahwa data yang dimigrasikan sudah lengkap dan akurat. Setidaknya, Anda harus menjalankan pernyataan SQL untuk memverifikasi bahwa tabel Anda ada di database AlloyDB untuk PostgreSQL yang dimigrasikan. Untuk perbandingan data yang lebih akurat antara database sumber dan tujuan, Anda dapat
mencoba menggunakan Alat Validasi Data open source.
Memverifikasi data tujuan dengan pernyataan SQL
Anda dapat menjalankan pernyataan SQL untuk memverifikasi bahwa tabel Anda ada di database AlloyDB untuk PostgreSQL yang dimigrasikan. Lakukan tindakan berikut:
Hubungkan ke instance Cloud SQL untuk PostgreSQL dengan alat tempat Anda dapat
menjalankan perintah SQL terhadap database yang dimigrasikan.
Untuk mengetahui informasi selengkapnya tentang cara terhubung ke instance Cloud SQL, lihat
Opsi koneksi
dalam dokumentasi Cloud SQL.
Jalankan perintah SQL untuk memverifikasi data yang dimigrasikan. Contoh:
Mencantumkan semua tabel dalam database:
SELECT*FROMpg_catalog.pg_tables;
Verifikasi isi tabel:
SELECT*FROMTABLE_NAME';
Verifikasi menggunakan Alat Validasi Data
Alat Validasi Data open source memungkinkan Anda melakukan perbandingan data yang sangat presisi antara dua database, tetapi alat ini memerlukan pembuatan koneksi jaringan ke database sumber dan tujuan Anda.
Langkah-langkah berikut menunjukkan contoh minimal:
Men-deploy atau menggunakan mesin virtual dengan akses ke sumber dan tujuan.
Di mesin virtual, buat folder untuk menginstal Alat Validasi Data.
Sebaiknya jalankan validasi ini selama replikasi untuk memastikan konsistensi
relatif. Kueri tabel besar mungkin membutuhkan waktu terlalu lama untuk dijalankan selama periode promosi yang singkat. Dalam kasus seperti itu, gunakan Alat Validasi Data untuk menambahkan filter guna mengurangi waktu proses atau menyiapkan daftar tabel untuk menyertakan subkumpulan tabel untuk validasi akhir.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-05 UTC."],[[["\u003cp\u003eThis guide details how to verify the successful migration of data from a source database to a Cloud SQL destination instance.\u003c/p\u003e\n"],["\u003cp\u003eYou can perform initial verification by checking for the existence of the migrated database instance and its tables in Cloud SQL.\u003c/p\u003e\n"],["\u003cp\u003eThe Data Validation Tool, an open-source utility, can be used to confirm the accuracy of data between the source and destination databases.\u003c/p\u003e\n"],["\u003cp\u003eTo use the Data Validation Tool, you must first install it on a virtual machine that has access to both the source and destination databases and then create the corresponding connections.\u003c/p\u003e\n"],["\u003cp\u003eThe Data Validation tool can also be used during replication to ensure relative data consistency.\u003c/p\u003e\n"]]],[],null,["# Verify a migration\n\nThis page describes how to confirm that your migrated data is complete and\naccurate. At a minimum, you should run SQL statements to verify that your tables\nexist in the migrated AlloyDB for PostgreSQL database. For a more precise\ndata comparison between the source and destination database,\nyou can\n[try using the open-source Data Validation Tool](#verify-dvt).\n\nVerify destination data with SQL statements\n-------------------------------------------\n\nYou can run SQL statements to verify that your tables\nexist in the migrated AlloyDB for PostgreSQL database. Do the following:\n\n1. Connect to your Cloud SQL for PostgreSQL instance with a tool where you can run SQL commands against your migrated databases. For more information on connecting to Cloud SQL instances, see\n [Connection options](/sql/docs/postgres/connect-overview#tools_for_connecting_to)\n in Cloud SQL documentation.\n\n2. Run SQL commands to verify your migrated data. For example:\n\n - List all tables in the database: \n\n ```sql\n SELECT * FROM pg_catalog.pg_tables;\n ```\n - Verify the table contents: \n\n ```sql\n SELECT * FROM TABLE_NAME';\n ```\n\nVerify using the Data Validation Tool\n-------------------------------------\n\nThe [open-source Data Validation Tool](https://github.com/GoogleCloudPlatform/professional-services-data-validator) lets you perform very precise\ndata comparisons between two databases, but it requires creating network\nconnections to your source and destination databases.\n\nThe following steps show a minimal example:\n\n1. Deploy or use a virtual machine with access to both the source and the destination.\n\n2. In the virtual machine, create a folder in which to install the Data Validation Tool.\n\n3. Navigate to this folder.\n\n4. Use [`pip`](https://pip.pypa.io/en/stable/) to install the Data Validation Tool.\n\n ```\n pip install google-pso-data-validator\n ```\n5. Create connections to the source Oracle database and the destination AlloyDB for PostgreSQL database:\n\n ```\n data-validation connections add -c source Oracle --host 'ip-address' --port port --user username --password pswd --database database-name\n data-validation connections add -c target Postgres --host 'ip-address' --port port --user username --password pswd --database database-name\n ```\n\n For example: \n\n ```\n data-validation connections add -c source Oracle --host '10.10.10.11' --port 1521 --user system --password pswd --database XE\n data-validation connections add -c target Postgres --host '10.10.10.12' --port 5432 --user postgres --password pswd --database postgres\n ```\n6. Create or generate a list of tables to compare data between the source and destination databases:\n\n ```\n export TABLES_LIST=$(data-validation find-tables --source-conn source --target-conn target --allowed-schemas schema-name)\n ```\n\n For example: \n\n ```\n export TABLES_LIST=$(data-validation find-tables --source-conn source --target-conn target --allowed-schemas public)\n ```\n7. Run full validation against all tables:\n\n ```\n data-validation validate column --source-conn source --target-conn target --tables-list \"${TABLES_LIST}\"\n ```\n\nWe suggest that you run this validation during replication to ensure relative\nconsistency. Large table queries may take too long to run during a small promotion\nwindow. In such cases, use the Data Validation Tool to add filters to reduce\nruntime or prepare the table list to include a subset of tables for the final\nvalidation."]]
