Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Database Migration Service memigrasikan semua data dari file cadangan yang Anda upload ke
bucket Cloud Storage, tetapi tidak semua fitur yang ada di database sumber Anda
mungkin tersedia di Cloud SQL untuk SQL Server. Tugas migrasi Database Migration Service
tidak memulihkan data yang termasuk dalam fitur yang tidak didukung, tetapi instance Cloud SQL tujuan Anda untuk SQL Server mungkin menghasilkan peringatan atau error dalam log.
Sebelum memilih untuk memigrasikan database SQL Server ke
Cloud SQL untuk SQL Server, pastikan Anda mempertimbangkan
Fitur SQL Server yang tidak tersedia untuk Cloud SQL
dalam dokumentasi Cloud SQL untuk SQL Server.
Batasan tambahan yang diketahui untuk migrasi SQL Server homogen ke
Cloud SQL untuk SQL Server dengan Database Migration Service mencakup hal berikut:
Database Migration Service dapat memigrasikan hingga maksimum 20 database per tugas
migrasi.
Anda hanya dapat menjalankan satu tugas migrasi untuk satu instance Cloud SQL untuk SQL Server
tujuan.
File cadangan Anda dapat memiliki ukuran maksimum 5 TB.
Anda dapat membuat stripe file cadangan lengkap menjadi file yang lebih kecil jika ukuran database Anda melebihi 5 TB. Setiap stripe dapat memiliki ukuran maksimum 5 TB.
Anda dapat menggunakan file cadangan dan log transaksi terenkripsi untuk migrasi.
Jika ingin menggunakan file cadangan terenkripsi, Anda harus mengenkripsi
setiap file cadangan (pencadangan penuh, diferensial, log transaksi) yang Anda gunakan untuk
database tertentu yang disertakan dalam migrasi.
Lihat
Menggunakan cadangan terenkripsi.
Instance SQL Server sumber Anda tidak dapat menggunakan model pemulihan sederhana.
Untuk informasi selengkapnya tentang model pemulihan, lihat
Model Pemulihan (SQL Server) dalam dokumentasi Microsoft.
Database Migration Service tidak memigrasikan
database master SQL Server,
informasi pengguna (seperti login pengguna), atau tugas yang bukan bagian dari database
tertentu.
Pemulihan point-in-time (PITR) tidak dapat diaktifkan di instance Cloud SQL tujuan selama migrasi. Anda dapat mengaktifkan fitur ini setelah
migrasi selesai.
[[["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 migrates data from uploaded backup files to Cloud SQL for SQL Server, but not all source database features may be supported.\u003c/p\u003e\n"],["\u003cp\u003eA single migration job can handle up to 20 databases, with only one job allowed per destination Cloud SQL for SQL Server instance.\u003c/p\u003e\n"],["\u003cp\u003eBackup files can be a maximum of 5 TB each, and if the database size exceeds 5TB, striping into smaller files is allowed, but must remain under the maximum file size.\u003c/p\u003e\n"],["\u003cp\u003eThe source SQL Server instance must not use the simple recovery model.\u003c/p\u003e\n"],["\u003cp\u003eThe migration service does not migrate the SQL Server \u003ccode\u003emaster\u003c/code\u003e database, user information, or jobs that are not linked to a specific database.\u003c/p\u003e\n"]]],[],null,["# Known limitations\n\nDatabase Migration Service migrates all data from the backup files you upload to the\nCloud Storage bucket, but not all features present in your source database\nmight be available in Cloud SQL for SQL Server. Database Migration Service migration jobs\ndon't restore data that falls under an unsupported feature, but your destination\nCloud SQL for SQL Server instance might produce warnings or errors in the\nlogs.\n\nBefore you choose to migrate your SQL Server databases to\nCloud SQL for SQL Server, make sure you consider\n[SQL Server features unavailable for Cloud SQL](/sql/docs/sqlserver/features#general_sql_server_features_unavailable_for)\nin Cloud SQL for SQL Server documentation.\n| **Note:** You can also use Google Cloud Migration Center to discover possible limitations or gaps in feature support for your specific scenario. See [Discover and import databases](/migration-center/docs/discover-and-import-databases) in the Migration Center documentation.\n\nAdditional known limitations for homogeneous SQL Server migrations to\nCloud SQL for SQL Server with Database Migration Service include the following:\n\n- Database Migration Service can migrate up to a maximum of 20 databases per migration\n job.\n\n- You can run only one migration job for a single destination Cloud SQL for SQL Server\n instance.\n\n- Your backup files can have a maximum size of 5 TB.\n\n- You can stripe your full backup file into smaller files if your database size\n exceeds 5 TB. Each stripe can have a maximum size of 5 TB.\n\n- You can use encrypted backup and transaction log files for your migration.\n If you want to use encrypted backup files, you must encrypt\n **every backup file** (full, differential, transaction log) you use for a\n specific database included in your migration.\n See\n [Use encrypted backups](/database-migration/docs/sqlserver/backup-file-encryption).\n\n- Your source SQL Server instance can't use the **simple recovery model** .\n For more information on recovery models, see\n See [Recovery Models (SQL Server)](https://learn.microsoft.com/en-us/sql/relational-databases/backup-restore/recovery-models-sql-server) in Microsoft documentation.\n\n- Database Migration Service doesn't migrate the [SQL Server `master` database](https://learn.microsoft.com/en-us/sql/relational-databases/databases/master-database),\n user information (such as user logins), or jobs that aren't a part of a specific\n database.\n\n - [Point-in-time recovery (PITR)](/sql/docs/sqlserver/backup-recovery/pitr) can't be enabled on your destination Cloud SQL instance during migration. You can enable this feature after the migration is complete."]]
