pingcap-inc
Official@pingcap-inc
PingCAP provides specialized database migration pathways for transitioning legacy and distributed relational systems into TiDB environments.
Agent Skills by pingcap-inc
Showing 9 vetted skills indexed across 2 GitHub repositories.
pingcap-incaurora-to-tidb-migration
Migrate Aurora MySQL schemas and data to TiDB with validation.
pingcap-incspanner-to-tidb-migration
Migrate Cloud Spanner schemas and data to TiDB Cloud.
pingcap-incoceanbase-to-tidb-migration
Automate OceanBase to TiDB migration with schema scanning, conversion, data loading, and validation.
pingcap-incneon-to-tidb-migration
Migrate Neon or PostgreSQL databases to TiDB with schema conversion and validation.
pingcap-incsqlserver-to-tidb-migration
Migrate SQL Server databases to TiDB with schema conversion, data loading, and validation.
pingcap-inccockroachdb-to-tidb-migration
Generate a CockroachDB to TiDB migration plan with schema, data, and procedural code validation.
pingcap-incsupabase-to-tidb-migration
Migrate Supabase databases to TiDB through phased assessment, conversion, and validation.
pingcap-incoracle-to-tidb-migration
Assess Oracle compatibility and migrate schemas, PL/SQL, and data to TiDB Cloud.
pingcap-incpantheon-issue-resolve
Orchestrate Pantheon issue resolution workflows from analysis through verification.
Frequently Asked Questions About pingcap-inc
FAQPage SchemaWhat specific database platforms can be migrated to TiDB?▼
These capabilities support migrations from Aurora MySQL, Cloud Spanner, OceanBase, Neon, PostgreSQL, SQL Server, CockroachDB, Supabase, and Oracle. Each path includes schema scanning, data loading, and validation to ensure integrity during the transition to TiDB.
Which engineering personas benefit from these migration capabilities?▼
Database administrators, site reliability engineers, and data architects tasked with re-platforming enterprise systems benefit from these migration paths. These resources provide structured assessment and conversion logic to minimize downtime and data loss during complex database migrations.
What are the primary phases involved in a migration process?▼
The migration process involves three core phases: schema assessment and conversion, data loading, and final validation. Each path is tailored to the source database's specific architecture, ensuring that procedural code, constraints, and data types are correctly mapped to the target TiDB environment.