Data Transmission Service:Deprecation of physical protocol for SQL Server migration

Change details

DTS will deprecate the cloud migration feature for SQL Server that uses the physical protocol. After this feature is deprecated, you will no longer be able to create migration tasks in the DTS Console where the source Database Type is SQL Server and the Access Method is Physical Protocol.

This change affects only the SQL Server cloud migration capability in the DTS Console that uses a DBS backup gateway or a proxy gateway. It does not affect data already migrated to the destination RDS SQL Server instance.

The scope of this deprecation includes:

• The capability to perform a cloud migration by creating a data migration task in the DTS Console with the source Database Type set to SQL Server and the Access Method set to Physical Protocol.

• The ability to migrate a self-managed SQL Server database from an ECS instance, an IDC, or another cloud server to an Alibaba Cloud RDS SQL Server instance by using the Physical Protocol Gateway (DBS Backup Gateway).

• The ability to deploy a proxy gateway on a bastion host to perform a cloud migration by using the Physical Protocol when the server that hosts the self-managed SQL Server cannot directly access the public network.

Deprecation timeline and impact

Note the following key dates and adjust your migration plan accordingly:

Impact on you

• If you have not created a physical protocol migration task: We recommend using the DTS logical data migration solution instead. To do this, perform the following steps:

  1. Log on to the DTS Console.

  2. In the left-side navigation pane, click Data Migration.

  3. Click Create Task. For the source database, set the Database Type to SQL Server and the Access Method to a network type such as Internet, Express Connect, VPN Gateway, or Smart Access Gateway, or Cloud Enterprise Network (CEN). For more information, see Migrate a self-managed SQL Server database to an RDS SQL Server instance.

• If you have an existing physical protocol migration task that is not started or in progress: You must complete the following operations before the 00:00:00 on October 30, 2026 (UTC+8) deadline:

  1. Log on to the DTS Console and click Data Migration in the left-side navigation pane.

  2. Find the target migration task, complete the precheck, and start the migration.

  3. After the Full Data Migration is complete, perform the cloud migration and service switchover during the Incremental Data Migration phase.

• If your cloud migration task is complete: This feature deprecation does not affect the data in your destination RDS SQL Server instance or its use.

• If you have deployed a DBS backup gateway or a proxy gateway: If the component is no longer needed, you can stop or uninstall it per your internal O&M policies.

Alternative solution

After the feature is deprecated, we recommend using the DTS logical data migration solution to migrate your SQL Server databases. For more information, see Migrate a self-managed SQL Server database to an RDS SQL Server instance.

Compared with physical protocol migration, logical data migration does not require you to install a physical protocol gateway on the source database server. You can connect to the source database using any access method supported by DTS and use features such as Full Data Migration and Incremental Data Migration. Depending on your source network environment, you can use an Internet such as Express Connect, VPN Gateway, or Smart Access Gateway, Cloud Enterprise Network (CEN), or Cloud Enterprise Network (CEN).

Before using logical data migration, confirm the following:

• The source SQL Server database account has the required permissions for schema migration, full migration, and incremental migration.

• The source database port, IP address whitelist, firewall, and security group policies are configured to allow access from DTS.

• The destination RDS SQL Server instance's capacity, version, number of databases, and account permissions meet the migration requirements.

• Data consistency is verified before the service switchover, and write operations to the source database are stopped or controlled during the switchover window.

FAQ

• Q: Will the data already migrated to RDS SQL Server be affected after the feature is deprecated?

  A: No. This deprecation only affects the ability to create and run SQL Server cloud migration tasks that use the physical protocol. It does not delete or modify any data already migrated to the destination RDS SQL Server instance.

• Q: Can I still create SQL Server migration tasks after the feature is deprecated?

  A: Yes. You can still create SQL Server migration tasks in the DTS Console, but you can no longer select Access Method as the Physical Protocol. You must use the logical data migration solution with other network access methods, such as Internet, Express Connect, VPN Gateway, or Smart Access Gateway, or Cloud Enterprise Network (CEN), to complete the migration.

• Q: What should I do with a physical protocol migration task that is in progress?

  A: You must complete the cloud migration and service switchover before the 00:00:00 on October 30, 2026 (UTC+8) deadline. After this deadline, the related task capabilities may no longer be available.

• Q: Do I need to uninstall the DBS backup gateway or proxy gateway that is already installed?

  A: If the component is no longer needed, you can stop or uninstall it per your internal O&M policies.

• Q: What should I do if I cannot complete the migration before the deadline?

  A: Submit a ticket or contact Alibaba Cloud technical support as soon as possible. Provide your instance information, task ID, source network environment, and estimated migration window so we can evaluate a mitigation plan.