Before you create a Data Transmission Service (DTS) task, you must prepare the environments that are required for the source or destination self-managed database.
Background information
DTS allows you to use a self-managed database as the source or destination database for data transmission. You must make preparations based on the scenario and then select the corresponding database type and access method when you configure the DTS task. For example, suppose the on-premises database to be migrated can be accessed over the Internet. After you make preparations, you can set Access Method to Public IP Address for the database when you configure the data migration task.
Preparations
Scenario | Network | Preparation | Task type | Access method |
The source or destination database is an on-premises database and can be accessed over the Internet. | Internet |
| Public IP Address | |
The source or destination database is an on-premises database but cannot be accessed over the Internet. | Cloud Enterprise Network (CEN) |
| Cloud Enterprise Network (CEN) | |
Database Gateway |
| Database Gateway | ||
VPN Gateway |
| Express Connect, VPN Gateway, or Smart Access Gateway | ||
Smart Access Gateway (SAG) |
| |||
Express Connect |
| |||
The source or destination database is hosted on an Elastic Compute Service (ECS) instance. | Virtual private cloud (VPC) | Add the CIDR blocks of DTS servers Note In this scenario, DTS automatically adds the CIDR blocks of DTS servers to the security settings of the ECS instance. However, if the source or destination database is hosted on multiple ECS instances, you must manually add the CIDR blocks of DTS servers to the security settings of the ECS instances. |
| Self-managed Database on ECS |