For homogeneous SQL Server migrations to Cloud SQL,
Database Migration Service requires that you first create and configure your
Cloud SQL destination instance. Perform the following steps:

1. [Create your destination instance](https://docs-0cloud-0google-0com.linkedin.net.nz/sql/docs/sqlserver/create-instance.md.txt). You can select the same
   SQL Server version as your source or a later version (2019, 2022, or
   2025) to upgrade during the migration (starting April 12, 2027, you won't be
   able to create new Cloud SQL for SQL Server 2017 instances; see
   [Database versions and version policies](https://docs-0cloud-0google-0com.linkedin.net.nz/sql/docs/sqlserver/db-versions.md.txt)).
   Make sure you use enough compute
   and memory resources to cover your migration needs and follow the requirements
   listed in
   [known limitations](https://docs-0cloud-0google-0com.linkedin.net.nz/database-migration/docs/sqlserver/known-limitations.md.txt).

2. Create and configure a dedicated migration user in your destination
   Cloud SQL instance. This user is required for Database Migration Service to successfully
   connect to your destination instance and monitor your data. You need to provide
   the username and password for this account at a later stage, when you
   [create the destination connection profile](https://docs-0cloud-0google-0com.linkedin.net.nz/database-migration/docs/sqlserver/create-destination-connection-profile.md.txt).

   1. Create the database user account in your destination Cloud SQL for SQL Server
      instance. See
      [Create and manage users](https://docs-0cloud-0google-0com.linkedin.net.nz/sql/docs/sqlserver/create-manage-users.md.txt) in the Cloud SQL documentation.

   2. Assign the following privileges to the user account:

      - For SQL Server 2019: `VIEW ANY DEFINITION` and `VIEW SERVER STATE`
      - For later versions: `VIEW ANY DEFINITION` and `VIEW SERVER PERFORMANCE STATE`

   For information on how to assign privileges to user accounts, see
   [Changing permissions for users](https://docs-0cloud-0google-0com.linkedin.net.nz/sql/docs/sqlserver/users.md.txt#changing-permissions) in the Cloud SQL documentation.
3. Grant the Cloud Storage permissions to the service account associated
   with your destination instance. This account is created after you create the
   destination instance.

   1. Check the email address associated with this service account on the
      Cloud SQL instance detail page. See
      [View instance information](https://docs-0cloud-0google-0com.linkedin.net.nz/sql/docs/sqlserver/instance-info.md.txt#service_account) in the Cloud SQL documentation.

   2. Add the `storage.objects.get`, and `storage.objects.list`
      permissions to the service account. For information on how to manage access
      with Identity and Access Management, see
      [Manage access to projects, folders, and organizations](https://docs-0cloud-0google-0com.linkedin.net.nz/iam/docs/granting-changing-revoking-access.md.txt)
      in the IAM documentation.

## What's next?

- [Create a migration job](https://docs-0cloud-0google-0com.linkedin.net.nz/database-migration/docs/sqlserver/create-migration-job.md.txt)