Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Anda dapat memigrasikan database SQL Server ke instance Cloud SQL untuk SQL Server dengan Database Migration Service menggunakan alur pencadangan dan pemulihan.
Pertama-tama, upload cadangan database lengkap dan file log transaksi ke bucket Cloud Storage. Database Migration Service kemudian secara aktif
memantau bucket Anda, dan terus mereplikasi data ke instance
Cloud SQL untuk SQL Server tujuan.
Halaman ini memberikan ringkasan fitur utama Database Migration Service
untuk migrasi SQL Server homogen:
Aliran data migrasi berkelanjutan memberikan ringkasan menyeluruh
tentang cara data Anda dipindahkan Google Cloud selama proses migrasi.
Pemantauan
memberikan pengantar untuk log dan metrik yang dapat
membantu Anda mengamati progres dan kondisi tugas migrasi.
Enkripsi membahas cara memigrasikan
dengan file cadangan SQL Server terenkripsi.
Database sumber dan tujuan yang didukung
Anda dapat menggunakan Database Migration Service untuk melakukan migrasi antara versi dan edisi SQL Server
yang sama, atau dari versi SQL Server
sebelumnya ke versi yang lebih baru yang didukung di Cloud SQL, selama
Anda mengikuti panduan kompatibilitas versi. Untuk informasi selengkapnya,
lihat upgrade versi dan edisi yang didukung untuk versi SQL Server
Anda dalam dokumentasi Microsoft. Misalnya, lihat
Upgrade versi dan edisi yang didukung (SQL Server 2022).
Tabel berikut mencantumkan semua database sumber dan tujuan SQL Server yang didukung:
Database sumber
Database tujuan
Amazon RDS
Cloud SQL untuk SQL Server versi 2022, 2019, 2017
SQL Server yang dikelola sendiri
(di lokasi atau di VM cloud apa pun yang Anda kontrol sepenuhnya)
Aliran data migrasi berkelanjutan
Untuk migrasi SQL Server homogen ke Cloud SQL,
Database Migration Service mendukung
alur
migrasi berkelanjutan. Dalam pendekatan ini, data Anda pertama kali
dimuat dari file cadangan database lengkap, lalu dari file cadangan diferensial,
lalu terus diperbarui berdasarkan file log transaksi yang Anda upload ke
bucket Cloud Storage khusus.
Gambar 1. Pergerakan data selama Database Migration Service untuk
migrasi SQL Server. (klik untuk memperbesar)
Pada tingkat tinggi, data Anda akan melalui fase migrasi sebagai berikut:
Anda mengupload file cadangan ke Cloud Storage.
Migrasi SQL Server berkelanjutan mengharuskan Anda terlebih dahulu mengambil
pencadangan penuh database sumber, lalu mengupload file cadangan ke
bucket Cloud Storage.
Untuk update berikutnya, Anda dapat secara opsional memberikan file pencadangan diferensial,
lalu mengupload file log transaksi.
Anda juga dapat mengotomatiskan pembuatan dan upload log transaksi berkelanjutan.
Untuk mengetahui informasi selengkapnya tentang cara mengotomatiskan pembuatan dan upload log transaksi berkelanjutan, lihat
Menjadwalkan pencadangan log transaksi.
Untuk mengetahui detail tentang cara Database Migration Service menggunakan berbagai jenis file cadangan
dalam migrasi SQL Server homogen, lihat
Jenis file cadangan yang didukung.
Saat tugas migrasi dimulai, Database Migration Service akan memuat cadangan database lengkap terbaru ke instance Cloud SQL untuk SQL Server tujuan.
Setelah pemuatan awal selesai, Database Migration Service akan beralih ke fase pemuatan
inkremental. Pada tahap ini, Database Migration Service melakukan hal berikut:
Jika tugas migrasi Anda dikonfigurasi untuk menggunakan file cadangan diferensial,
Database Migration Service akan memindai folder diff dan memuat file cadangan
diferensial ke instance tujuan Anda. Jika tugas migrasi Anda dikonfigurasi
untuk menggunakan file cadangan diferensial, tetapi Database Migration Service tidak dapat menemukannya
di bucket Cloud Storage, tugas migrasi akan menampilkan error
saat terus-menerus menelusuri folder diff untuk menemukan file cadangan
diferensial.
Database Migration Service memuat file cadangan diferensial hanya sekali, di awal
fase pemuatan inkremental. Saat tugas migrasi dilanjutkan untuk menggunakan
file log transaksi, tidak ada file cadangan diferensial baru yang dikenali saat
Anda menguploadnya ke folder diff.
Sekarang, Database Migration Service terus memindai bucket Cloud Storage Anda
untuk menemukan file cadangan log transaksi yang akan direplikasi di instance tujuan.
Saat data baru muncul di database sumber, Anda dapat terus mengekspor file cadangan log transaksi dan menguploadnya ke bucket Cloud Storage yang sama. Database Migration Service mengambil semua file cadangan log transaksi baru dan
mereplikanya di database tujuan.
Anda dapat menghentikan replikasi yang sedang berlangsung dan mempromosikan tugas migrasi saat ingin
mengganti aplikasi agar menggunakan instance tujuan Cloud SQL untuk SQL Server
sebagai database produksi. Untuk panduan migrasi langkah demi langkah yang mendetail, lihat
panduan migrasi Cloud SQL untuk SQL Server.
Pemantauan
Gambar 2. Contoh diagram visibilitas di Database Migration Service.
(klik untuk memperbesar)
Database Migration Service menyediakan kemampuan logging dan observasi yang ekstensif untuk membantu Anda memantau progres migrasi. Fitur ini mencakup diagnostik real-time untuk penundaan replikasi dan pemrosesan file cadangan log transaksi, serta log mendetail untuk status tugas migrasi dan kondisi instance tujuan Cloud SQL untuk SQL Server.
Database Migration Service sepenuhnya kompatibel dengan
cadangan SQL Server terenkripsi. Jika Anda mengupload kunci enkripsi ke Google Cloud, Database Migration Service dapat mendekripsi data Anda dengan aman dan memuat data tersebut ke instance tujuan Cloud SQL untuk SQL Server tanpa membahayakan keamanan data Anda.
[[["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\u003eDatabase Migration Service allows the migration of SQL Server databases to Cloud SQL for SQL Server using a backup and restore method, where full database backups and transaction logs are uploaded to Cloud Storage.\u003c/p\u003e\n"],["\u003cp\u003eThe service supports various source databases, including Amazon RDS and self-managed SQL Servers, and can migrate between different SQL Server versions as long as version compatibility guidelines are met.\u003c/p\u003e\n"],["\u003cp\u003eData migration occurs in a continuous flow, starting with a full backup, followed by an optional differential backup, and then ongoing updates from transaction log files uploaded to a designated Cloud Storage bucket.\u003c/p\u003e\n"],["\u003cp\u003eDatabase Migration Service offers monitoring capabilities, including real-time diagnostics and detailed logs, to track the progress and health of the migration process.\u003c/p\u003e\n"],["\u003cp\u003eThe migration service can handle encrypted SQL Server backups, ensuring data security by decrypting the files using an uploaded encryption key during the migration process.\u003c/p\u003e\n"]]],[],null,["# Database Migration Service for SQL Server\n\nYou can migrate SQL Server databases to Cloud SQL for SQL Server\ninstances with Database Migration Service by using a backup and restore flow.\nYou first upload the full database backup and transaction\nlog files to a Cloud Storage bucket. Database Migration Service then actively\nmonitors your bucket, and continuously replicates your data to the destination\nCloud SQL for SQL Server instance.\n\nThis page provides an overview of the key Database Migration Service\nfeatures for homogeneous SQL Server migrations:\n\n- [Supported source and destination](#supported-src-and-dest) lists all SQL Server\n versions supported by Database Migration Service.\n\n- [Continuous migrations data flow](#data-flow-migration-types) provides an end-to-end overview\n of how your data moves in Google Cloud during the migration process.\n\n- [Monitoring](#monitoring)\n gives an introduction for logs and metrics that can\n help you observe the progress and health of your migration job.\n\n- [Encryption](#securing-migration-jobs) looks at how you can migrate\n with encrypted SQL Server backup files.\n\nSupported source and destination databases\n------------------------------------------\n\nYou can use Database Migration Service to migrate between the same SQL Server\nversion and edition, or from earlier versions of\nSQL Server to later versions supported in Cloud SQL, as long\nas you follow the version compatibility guidelines. For more information,\nsee the supported version and edition upgrades for your SQL Server\nversion in Microsoft documentation. For example, see\n[Supported version and edition upgrades (SQL Server 2022)](https://learn.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2022?view=sql-server-ver16#upgrades-from-earlier-versions-to-sql-server-2022).\n\nThe following table lists all supported SQL Server source and destination\ndatabases:\n\nContinuous migrations data flow\n-------------------------------\n\nFor homogeneous SQL Server migrations to Cloud SQL,\nDatabase Migration Service supports the\n[continuous migration](/database-migration/docs/overview#migrationconcepts) flow. In this approach, your data is first\nloaded from a full database backup file, then from a differential backup file,\nand then continuously updated based on transaction log files you upload to\na dedicated Cloud Storage bucket.\n[](#lightbox-trigger) **Figure 1.** Data movement during Database Migration Service for SQL Server migrations. (click to enlarge)\n\nAt a high level, your data moves through the migration phases as follows:\n\n1. You upload your backup files to Cloud Storage.\n\n Continuous SQL Server migrations require that you first take a\n full backup of your source database, and then upload the backup file to\n a Cloud Storage bucket.\n For subsequent updates, you can optionally provide a differential backup file,\n and then upload transaction log files.\n You can also automate continuous transaction log creation and uploads.\n - For more information on automating continuous transaction log creation and\n uploads, see\n [Schedule transaction log backups](/database-migration/docs/sqlserver/automate-backup-exports).\n\n - For details on how Database Migration Service uses different types of backup files\n in homogeneous SQL Server migrations, see\n [Supported backup file types](/database-migration/docs/sqlserver/supported-backup-files).\n\n2. When the migration job starts, Database Migration Service loads the latest full\n database backup to the destination Cloud SQL for SQL Server instance.\n\n3. Once the initial load is complete, Database Migration Service switches to the incremental\n load phase. At this point, Database Migration Service performs the following:\n\n 1. If your migration job is configured to use a differential backup file,\n Database Migration Service scans the `diff` folder and loads differential backup\n files to your destination instance. If your migration job is configured\n to use a differential backup file, but Database Migration Service can't find it\n in the Cloud Storage bucket, the migration job shows an error\n while continuously searching the `diff` folder for the differential\n backup file.\n\n Database Migration Service loads differential backup files only once, at the beginning\n of the incremental load phase. When the migration job proceeds to work with\n transaction log files no new differential backup files are recognized when\n you upload them to the `diff` folder.\n 2. Now Database Migration Service continuously scans your Cloud Storage bucket\n for transaction log backup files to replicate on your destination instance.\n\n4. As new data shows up in your source database, you can keep exporting\n the transaction log backup files and uploading them to the same Cloud Storage\n bucket. Database Migration Service picks up all new transaction log backup files and\n replicates them on the destination database.\n\nYou can stop the ongoing replication and promote the migration job when you want\nto switch your application to so that it uses the Cloud SQL for SQL Server\ndestination instance as the production database. For a detailed step-by-step\nmigration guide, see\n[Cloud SQL for SQL Server migration guide](/database-migration/docs/sqlserver/guide).\n\nMonitoring\n----------\n\n[](#lightbox-trigger) **Figure 2.** Sample observability diagram in Database Migration Service. (click to enlarge)\n\nDatabase Migration Service provides extensive logging and observability capabilities\nto help you monitor the migration progress. These features include real-time\ndiagnostics for replication delay and transaction log backup file processing,\nas well as detailed logs for Cloud SQL for SQL Server destination instance health\nand migration job state.\n\nFor more details, see\n[Migration job metrics](/database-migration/docs/sqlserver/migration-job-metrics).\n\nEncryption\n----------\n\nDatabase Migration Service is fully compatible with\n[encrypted SQL Server backups](https://learn.microsoft.com/en-us/sql/relational-databases/backup-restore/backup-encryption). If you upload your\nencryption key to Google Cloud, Database Migration Service can safely decrypt\nyour data and load it to the Cloud SQL for SQL Server destination instance without\ncompromising your data security.\n\nFor more details, see\n[Encrypted SQL Server backup files](/database-migration/docs/sqlserver/backup-file-encryption).\n\nWhat's next\n-----------\n\n- To learn more about SQL Server data and feature support in\n Database Migration Service, see\n [Known limitations](/database-migration/docs/sqlserver/known-limitations).\n\n- To get a complete, step-by-step migration walkthrough, see\n [Cloud SQL for SQL Server migration guide](/database-migration/docs/sqlserver/guide)."]]
