The TiDB Connector
Archive TiDB distributed SQL databases at the point of application migration or compliance mandate. Retain HTAP workload history in open Lakehouse format — without TiDB infrastructure costs.
🌟 Featured in Gartner® Hype Cycle™ for Data Management
Connectors
Data Governance
Enterprise Clients
Talk to a Connector Expert
TiDB Archiving — Done Right
TiDB’s HTAP design makes it a natural fit for high-volume transactional applications — payments, orders, user records — where the same data serves both operational and analytical queries. That is its strength for live workloads. For multi-year compliance archives, it is an expensive way to store data that no active application is querying.
Archon’s TiDB Connector extracts tables, schemas, TiFlash analytical replicas, and historical datasets from TiDB 5.x through 8.x and TiDB Cloud — and archives them into open Parquet/Delta Lake format. Compliance retention handled without the HTAP infrastructure cost.
- Tables, schemas, views, transactional records, TiFlash analytical replicas, audit logs via JDBC (MySQL-compatible connector)
- TiDB 5.x, 6.x, 7.x, 8.x and TiDB Cloud (Serverless and Dedicated) supported
- Cross-table query via Archon Analyzer — no TiDB runtime post-archive
- GDPR, PCI DSS, PBOC, CBIRC, and SOX retention policy support
Capabilities
Everything You Need for TiDB Data Operations
Full schema and historical data extraction
All TiDB tables, views, and schema structures extracted with relational integrity and column-level metadata preserved. No custom extraction scripts or database administrator involvement required.
TiFlash analytical replica archiving
TiFlash columnar replicas used for analytical workloads extracted alongside transactional data — providing a complete archive of both OLTP and OLAP datasets from the same TiDB environment.
Application retirement and infrastructure cost elimination
TiDB instances retained solely for compliance data access decommissioned after Archon archives the historical dataset. HTAP infrastructure, licensing, and support costs eliminated while regulatory compliance is maintained.
Compliance audit trail support
Audit tables, transaction logs, and schema-level metadata preserved in the Archon archive — satisfying GDPR, PCI DSS, PBOC, CBIRC, and SOX requirements, accessible without TiDB infrastructure.
Use Cases
How Enterprises Use the TiDB Connector
01 Fintech and payment platform archiving
Payment platforms and fintech organizations storing transactional records, order history, and user account data in TiDB archive aged datasets through Archon — satisfying PCI DSS and PBOC financial data retention requirements.
02 Database migration historical archiving
Migrations from TiDB to modern databases use Archon to archive complete historical data before cutover — full operational record preserved in open Parquet format, independently of the migration.
03 License and infrastructure cost elimination
TiDB instances running solely for compliance access decommissioned after Archon archives the data. HTAP licensing, support, and infrastructure costs eliminated.
04 Compliance audit and eDiscovery support
Compliance audits and legal proceedings requiring TiDB records from prior years fulfilled through Archon Analyzer — without database administrator involvement or a live TiDB instance.
Technical Specifications
| Specification | Details |
|---|---|
| Connection Method | JDBC (MySQL-compatible connector) |
| Supported Versions | TiDB 5.x, 6.x, 7.x, 8.x; TiDB Cloud (Serverless and Dedicated) |
| Data Scope | Tables, schemas, views, transactional records, TiFlash analytical replicas, audit logs |
| Output Format | Parquet, Delta Lake, Avro, XML, CSV, TXT, TSV, Excel |
| Metadata Handling | Schema structure, indexes, constraints, column definitions |
| Transformation Rules | 1,000+ built-in; TiDB data type normalization included |
| Retention schedules | GDPR, PCI DSS, PBOC, CBIRC, SOX Section 802 |
| Security & Compliance | TLS 1.3 in transit · AES-256 at rest · WORM · Cryptographic hashing |
How It Works
Up and Running in 4 Steps
01
Connect to TiDB
Authenticate via JDBC (MySQL-compatible connector) to TiDB 5.x–8.x or TiDB Cloud. Archon auto-discovers all databases, schemas, tables, views, and stored procedure definitions. 02
Map & Configure
Define schema and table scope, TiFlash replica handling, data type normalization rules, and jurisdiction-specific retention schedules. Configure PII masking for GDPR compliance. 03
Validate & Preview
Dry-run against sample TiDB databases. Quality report flags null primary keys, data type normalization issues, and schema anomalies. 04
Archive & Monitor
Cryptographic hashes and trusted timestamps applied per table. Data searchable via Archon Analyzer on ingestion.FAQ
Common Questions About the TiDB Connector
- 1. Does Archon support TiDB without requiring DBA involvement?
Yes. Read-only JDBC extraction — no DBA scripts, administrative privileges, or custom extraction code required.
- 2. Is archived TiDB data queryable without the TiDB runtime?
Yes. Open Parquet/Delta Lake format — queryable via Archon Analyzer, Apache Spark, Amazon Athena, or any Lakehouse query engine.
- 3. Does archived TiDB data satisfy GDPR and compliance retention requirements?
Yes. WORM-immutable, cryptographically hashed archive satisfies GDPR Article 5 and applicable sector-specific retention mandates.
Ready to archive your TiDB data and retire the dependency?
Talk to an Archon connector specialist at archondatastore.com. Free consultation, no commitment, reply within 24 hours.
