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
masterdatabase, 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.