Stay organized with collections
Save and categorize content based on your preferences.
Database Migration Service migrates all data from the backup files you upload to the
Cloud Storage bucket, but not all features present in your source database
might be available in Cloud SQL for SQL Server. Database Migration Service migration jobs
don't restore data that falls under an unsupported feature, but your destination
Cloud SQL for SQL Server instance might produce warnings or errors in the
logs.
Before you choose to migrate your SQL Server databases to
Cloud SQL for SQL Server, make sure you consider
SQL Server features unavailable for Cloud SQL
in Cloud SQL for SQL Server documentation.
Additional known limitations for homogeneous SQL Server migrations to
Cloud SQL for SQL Server with Database Migration Service include the following:
Database Migration Service can migrate up to a maximum of 20 databases per migration
job.
You can run only one migration job for a single destination Cloud SQL for SQL Server
instance.
Your backup files can have a maximum size of 5 TB.
You can stripe your full backup file into smaller files if your database size
exceeds 5 TB. Each stripe can have a maximum size of 5 TB.
You can use encrypted backup and transaction log files for your migration.
If you want to use encrypted backup files, you must encrypt
every backup file (full, differential, transaction log) you use for a
specific database included in your migration.
See
Use encrypted backups.
Your source SQL Server instance can't use the simple recovery model.
For more information on recovery models, see
See
Recovery Models (SQL Server) in Microsoft documentation.
Database Migration Service doesn't migrate the
SQL Server master database,
user information (such as user logins), or jobs that aren't a part of a specific
database.
Point-in-time recovery (PITR) can't be enabled on your destination
Cloud SQL instance during migration. You can enable this feature after
the migration is complete.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 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,[]]
