Database Transmission Service
Database Transmission Service
Database Transmission Service
Document
What's new
Overview
Constraints and limits
Billing
Pre-check items
Permission management
Getting started
Quick start guide for data migration
Quick start guide for data subscription
Quick start guide for data synchronization
Data migration
Creating a data migration task for MySQL
Volcano Engine RDS for MySQL as the source
Volcano Engine veDB for MySQL as the source
MySQL connected over public network as the source
MySQL connected over express network as the source
Creating a data migration task for PostgreSQL
Volcano Engine RDS for PostgreSQL as the source
PostgreSQL connected over public network as the source
PostgreSQL connected over express network as the source
Creating a data migration task for SQL Server
Volcano Engine SQL Server as the source
SQL Server connected over public network as the source
SQL Server connected over express network as the source
Creating a data migration task for Redis
Volcano Engine Cache for Redis as the source
Redis connected over public network as the source
Redis connected over express network as the source
Creating a data migration task for MongDB
Volcano Engine Document Database for MongoDB as the source
MongoDB connected over public network as the source
MongoDB connected over express network as the source
Creating a data migration task for Supabase
Supabase connected over public network as the source
Supabase connected over express network as the source
Data subscription
Creating a data subscription task for MySQL
Creating a data subscription task for PostgreSQL
Consuming subscription data
Data synchronization
Creating a data synchronization task for MySQL
Volcano Engine RDS for MySQL as the source
Volcano Engine veDB for MySQL as the source
MySQL connected over public network as the source
MySQL connected over express network as the source
Creating a data synchronization task for Redis
Volcano Engine Cache for Redis as the source
Redis connected over public network as the source
Redis connected over express network as the source
Creating a data synchronization task for PostgreSQL
Volcano Engine RDS for PostgreSQL as the source
PostgreSQL connected over public network as the source
PostgreSQL connected over express network as the source
Creating a data synchronization task for MongoDB
Volcano Engine Database for MongoDB as the source
MongoDB connected over public network as the source
MongoDB connected over express network as the source
Creating a data synchronization task for Milvus
ETL task management
(Beta) Data verification
(Beta) Migration evaluation
Monitoring and alerts
Best practices
Data migration
Data subscription
API reference
Billing
Data transmission
Data subscription (consumer group management)
Data verification
Migration evaluation
Pre-check
Appendix
SDK reference
FAQs
Common general questions
Pre-check
Troubleshooting
- Documentation
Database Transmission ServiceFAQsCommon general questionsAccess security and business impact FAQ
Copy page
Download PDFCommon general questions
Access security and business impact FAQ
Copy pageDownload PDFAccess security and business impact FAQ
Before accessing Database Transmission Service (DTS), you may be concerned about its impact on source database data security and business operations. This topic answers key questions about data integrity, table-locking mechanisms, and resource usage:
Will the source database data be deleted or modified?
No.
- Read-only actions: DTS only executes SELECT read operations on the source end and will never write, update, or delete source database data.
- Data security: the migration process does not change any content in the source database, ensuring absolute safety of source end data.
Will tables be locked during migration?
No.
- Lock-free migration: DTS will not lock tables in the source database during the entire lifecycle of full migration and incremental synchronization.
- Business transparency: the source end's data tables always maintain normal read and write access, with very low business awareness.
Does incremental migration or synchronization affect business continuity?
No, it actually helps ensure continuity.
- Real-time synchronization: incremental migration captures and synchronizes source end change data in real time, allowing business to continue running on the source end during migration.
- Smooth switching: you can perform final cutover during off-peak hours, reducing downtime to minutes and minimizing business impact.
Can i manually end a migration task during a full migration?
Not recommended/not allowed.
- System managed: full migration tasks automatically flow and end by the system.
- Risk prompt: do not forcibly manually terminate tasks during full execution, as this likely causes incomplete or abnormal destination data states.
- Correct action: if termination is needed, wait for the full migration phase to complete automatically before stopping.
Will the pressure on the source database increase during migration? How to optimize?
During the full migration phase, data is mainly pulled through SELECT, which does cause certain I/O and network overhead. To reduce the impact on core business, the following measures are recommended:
- Off-peak execution: start the full migration task during business off-peak hours (such as late night).
- Rate limiting: adjust the full migration rate in Database Transmission Service (DTS) configuration to proactively limit read pressure on the source database.
- Resource isolation: ensure the source database has dedicated connections and bandwidth resources to avoid competing with core business for maximum bandwidth.
Last updated: 2026.08.13 11:47:37
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
