BladePipe 1.7.0: Stronger alerts, Broader DB support, Faster KingbaseES scanning.
Skip to main content

TDSQL-C

BladePipe supports TDSQL-C as a source and target connector for real-time data integration, migration, synchronization, and analytics pipelines.

TDSQL-C

Source
Supported
Target
Supported

Build production data pipelines with TDSQL-C

BladePipe supports TDSQL-C for database migration, real-time synchronization, CDC replication, verification, and analytics pipelines.

TDSQL-C data source overview

TDSQL-C is Tencent Cloud's enterprise-grade cloud-native database, MySQL-compatible with high availability and elasticity.

Real-time movement

Build low-latency TDSQL-C pipelines for fresh data delivery instead of batch-only movement.

Full and incremental flow

Use TDSQL-C as a source for initial loading and ongoing incremental updates where the connector supports it.

Operational control

BladePipe provides visual setup, monitoring, retry, and operational workflows for production data teams.

Enterprise readiness

Keep network, permission, and deployment choices explicit so pipelines fit cloud, BYOC, and on-premise environments.

Common TDSQL-C pipeline patterns

1

TDSQL-C to ClickHouse, StarRocks, or Doris for real-time analytics

Synchronize TDSQL-C changes into analytical databases so orders, users, and business metrics can be queried with low latency.

2

TDSQL-C to Kafka for CDC event streaming

Convert TDSQL-C table changes into CDC events for message-driven services, search indexing, and real-time consumers.

3

TDSQL-C to PostgreSQL, MySQL, or Oracle for database migration

Combine full migration with incremental catch-up to reduce downtime and keep source and target data consistent.

Start building TDSQL-C data pipelines

Use BladePipe to connect TDSQL-C, validate the first pipeline, and move from testing to production with observable data movement.

TDSQL-C connector FAQ

Can BladePipe use TDSQL-C as a source?

Can BladePipe write data into TDSQL-C?

What is a common TDSQL-C data pipeline?