Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Bagian ini memberikan ringkasan tentang cara memigrasikan database Anda ke
Spanner. Proses untuk bermigrasi ke Spanner mungkin bervariasi, bergantung pada faktor seperti database sumber, ukuran data, persyaratan periode nonaktif, kompleksitas kode aplikasi, skema sharding, fungsi atau transformasi kustom, dan strategi failover dan replikasi.
Migrasi Spanner standar melibatkan tahap-tahap berikut:
Bergantung pada tahap migrasi yang Anda jalani, Anda
mungkin perlu berkonsultasi dengan administrator jaringan, administrator database, atau developer aplikasi organisasi untuk menyelesaikan langkah-langkah migrasi yang diuraikan.
Anda dapat menggunakan tahap migrasi tingkat tinggi yang dijelaskan sebelumnya jika ingin
memindahkan dump satu kali ke Spanner, atau menyelesaikan migrasi produksi
berskala besar. Bergantung pada kasus penggunaan, tindakan yang Anda lakukan di setiap
tahap dapat berubah secara signifikan.
[[["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."],[],[],null,["# Migration overview\n\nThis section provides an overview of how to migrate your database to\nSpanner. The process to migrate to Spanner might vary\ndepending on factors like your source database, data size, downtime requirements,\napplication code complexity, sharding schema, custom functions or\ntransformations, and failover and replication strategies.\n\nA typical Spanner migration involves the following stages:\n\n1. [Assess your migration](/spanner/docs/assess-migration).\n2. [Migrate your schema](/spanner/docs/schema-migration).\n3. [Modify your application code](/spanner/docs/application-migration).\n4. [Optimize your schema and application performance](/spanner/docs/optimize-schema-performance).\n5. [Migrate your data](/spanner/docs/data-migration).\n6. [Validate the migration](/spanner/docs/data-validation).\n7. [Configure cutover and fallback mechanisms](/spanner/docs/cutover-fallback-mechanisms).\n\nDepending on the stage of the migration you're in, you\nmight need to consult your organization's network administrator, database\nadministrator, or application developers to complete that migration steps\noutlined.\n\nYou can use the previously described high-level migration stages if you want to\nmove a one-time dump into Spanner, or complete a large-scale\nproduction migration. Depending on your use case, what you do in each of the\nstages can change significantly.\n\nSource-specific migration guides\n--------------------------------\n\n- MySQL: [Migrate from MySQL to Spanner](/spanner/docs/migrating-mysql-to-spanner)."]]
