Migrate and synchronize data from PolarDB-X 2.0 to Tablestore by using Data Transmission Service (DTS).
Background information
Data Transmission Service (DTS) is a real-time data streaming service provided by Alibaba Cloud that supports data exchange between relational databases (RDBMS), NoSQL databases, and online analytical processing (OLAP) systems. DTS integrates data synchronization, migration, subscription, integration, and processing to help you build a secure, scalable, and highly available data architecture. For more information, see Data Transmission Service (DTS).
Scenarios
Big data analytics and processing
Migrate large volumes of PolarDB business data to Tablestore for reporting and analytics. Tablestore provides a distributed architecture with high-concurrency read and write capabilities, enabling fast ad hoc queries suited for big data business intelligence (BI) and OLAP scenarios.
Log and event data processing
Migrate large volumes of log and event data from internet services, IoT devices, or applications to Tablestore for efficient storage and analysis. Tablestore handles semi-structured and unstructured data well, simplifying log analysis, monitoring, alerting, and trend prediction.
Cost optimization and archiving
As data volume grows, migrate infrequently accessed historical data from costly relational databases to Tablestore. This reduces storage costs while keeping data accessible for compliance audits or historical analysis.
Data import solutions
Select an import solution based on your data migration scenario.
Import solution | Description |
Data migration moves data to the cloud from on-premises databases, self-managed databases on ECS instances, or third-party cloud databases. It is a one-time task, and you can release the instance after the migration is complete. Migration types include schema migration, full migration, and incremental migration. Incremental migration provides limited data synchronization capabilities. For example, it does not support modifying synchronization objects online or two-way synchronization. | |
Data synchronization keeps two data sources consistent in real time. It applies to active geo-redundancy, data disaster recovery, cross-border synchronization, query and report offloading, cloud BI, and real-time data warehouses. Unlike migration, synchronization runs continuously after you create the task. Synchronization types include schema synchronization, full synchronization, and incremental synchronization. |
How data import works
How data migration works
Data migration consists of three phases: schema migration, full data migration, and incremental data migration. To keep the source database operational during migration, select all three migration types when you configure the task.
How data synchronization works
DTS synchronizes data changes between two data sources in real time, often transferring data from an online transactional processing (OLTP) database to an OLAP database. Data synchronization consists of two phases:
Initial synchronization: DTS begins by collecting incremental data, and then loads the structure and historical data from the source database to the target database.
Real-time data synchronization: After the initial synchronization is complete, DTS continuously synchronizes data changes to keep the source and destination databases consistent.
Billing
Data migration
| Migration type | Instance configuration fee | Internet traffic fee |
|---|---|---|
| Schema migration and full data migration | Free | Free |
| Incremental data migration | Charged. See Billing overview. | — |
Data synchronization
|
Synchronization type |
Pricing |
|
Schema synchronization and full data synchronization |
Free of charge. |
|
Incremental data synchronization |
Charged. For more information, see Billing overview. |
Tablestore
Importing data into Tablestore incurs storage fees based on the data volume.
When you access Tablestore using a migration tool, Tablestore bills read and write requests based on read/write throughput. The billing also depends on the instance type and whether you use pay-as-you-go or reserved read/write CUs.
NoteFor more information about instance types and Capacity Units (CUs), see Instances and Read/write throughput.