Category | Description |
Supported version | 1. Source database Self-built MongoDB (IDC self-built databases and self-built databases on Cloud Virtual Machine (CVM) instances) 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0. MongoDB 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0 from third-party cloud vendors. TencentDB for MongoDB 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0. 2. Target database TencentDB for MongoDB 4.0, 4.2, 4.4, 5.0, 6.0, and 7.0. |
Impact on the source database | When Data Transfer Service (DTS) is used to perform full data synchronization, it occupies certain resources of the source instance, which may cause the source instance load to increase and add pressure to the database. If your database configuration is low, it is recommended to perform this operation during off-peak hours. |
Impact on the target database | During synchronization, DTS is used along with the system service account to create a table named based on the task ID (such as dts-xxxxx) in the target TencentDTSData database. This table is used to record CHECKPOINT, enabling resumable transfer in case of task interruption. |
Synchronization type | Full and incremental data synchronization are supported. |
Synchronization object | Databases and collections. |
Supported SQL statements | 1. DML INSERT, UPDATE, and DELETE. 2. DDL INDEX: createIndexes, createIndex, dropIndex, and dropIndexes. COLLECTION: createCollection, drop, collMod, renameCollection, and convertToCapped. DATABASE: dropDatabase and copyDatabase. DDL operations for replica sets and sharded clusters are supported. |
Operation restrictions | 1. Do not perform the following operations during synchronization. Otherwise, they will cause the synchronization task to fail. Do not modify or delete user information (including usernames, passwords, and permissions) and port numbers in the source and target databases. Do not perform Oplog cleanup operations on the source database. During the incremental synchronization phase, do not delete the target TencentDTSData database. 2. where condition filtering is currently not supported. 3. Renaming databases or tables is currently not supported. |
Feedback