The Google Cloud SQL Connector
Archive Google Cloud SQL databases; MySQL, PostgreSQL, and SQL Server editions, to cost-optimized Lakehouse storage. Satisfy multi-year retention obligations without indefinite Cloud SQL compute costs.
🌟 Featured in Gartner® Hype Cycle™ for Data Management
Connectors
Data Governance
Enterprise Clients
Talk to a Connector Expert
Google Cloud SQL Archiving for Compliance Retention and Cost Management
Archon’s Google Cloud SQL Connector extracts tables, schemas, and historical data from Cloud SQL for MySQL, Cloud SQL for PostgreSQL, and Cloud SQL for SQL Server, and archives them into open Parquet/Delta Lake format on GCS-based Lakehouse or multi-cloud storage. Built for compliance and data engineering teams managing long-term retention mandates on GCP-native applications.
Cloud SQL automated backups retain data for a maximum of 365 days, not the 5, 7, or 10 years many regulated industries require. Archon bridges that gap with a separate, immutable compliance archive that satisfies regulators without requiring Cloud SQL instances to remain active.
- JDBC extraction from Cloud SQL for MySQL, PostgreSQL, and SQL Server
- Tables, schemas, views, audit logs, and change records captured
- Schema structure and relational metadata preserved in open Parquet format
- Cross-schema query via Archon Analyzer, no Cloud SQL compute costs post-archive
- GDPR, HIPAA, PCI DSS, and SOX retention policy support
Capabilities
Everything You Need for Google Cloud SQL Data Operations
Multi-Engine Cloud SQL Archiving
Archon extracts from Cloud SQL for MySQL, Cloud SQL for PostgreSQL, and Cloud SQL for SQL Server, with engine-specific extraction and schema normalization applied automatically. A single Archon configuration handles all Cloud SQL engine variants.
Beyond 365-Day Backup Retention
Cloud SQL automated backups retain data for up to 365 days. For GDPR, HIPAA, and SOX retention obligations spanning years, Archon provides a separate, WORM-immutable archive layer that satisfies regulators without Cloud SQL instance costs.
Cloud Application Retirement Data Preservation
GCP-native applications built on Cloud SQL are retired regularly. Archon archives the Cloud SQL database, including schema structure and audit logs, before the application is shut down, ensuring compliance access without Cloud SQL infrastructure.
Multi-Cloud Compliance Archiving
Organizations consolidating data from GCP, AWS, and Azure applications into a unified compliance repository use Archon's Cloud SQL connector alongside AWS Aurora and Azure SQL connectors, delivering a single Lakehouse archive across cloud platforms.
Use Cases
How Enterprises Use the Google Cloud SQL Connector
01 Long-Term Regulatory Compliance on GCP
Financial services, healthcare, and government entities with multi-year retention obligations on Cloud SQL data use Archon to satisfy those mandates, without keeping Cloud SQL instances active beyond the application lifecycle.
02 Cloud SQL Cost Reduction
GCP applications accumulate Cloud SQL storage on cold data at full instance pricing. Archon offloads those tables to GCS Lakehouse at a fraction of Cloud SQL costs, with no loss of query access via Archon Analyzer.
03 GCP Application Retirement
Cloud-native applications built on Cloud SQL are decommissioned after Archon archives the underlying database. Cloud SQL instance costs are eliminated while compliance access is maintained indefinitely.
04 Multi-Cloud Archive Consolidation
Enterprises managing data across GCP, AWS, and Azure applications archive Cloud SQL data alongside Aurora and Azure SQL data in a unified Lakehouse compliance repository, with a single search interface via Archon Analyzer.
Technical Specifications
| Specification | Details |
|---|---|
| Connection Method | JDBC via Cloud SQL Auth Proxy or direct IP |
| Supported Versions | Cloud SQL for MySQL (5.7, 8.0), Cloud SQL for PostgreSQL (12-16), Cloud SQL for SQL Server |
| Data Scope | Tables, schemas, views, audit logs, change records |
| Output Format | Parquet, Delta Lake, Avro, CSV, TSV |
| Metadata Handling | Schema structure, indexes, constraints, foreign keys, column definitions |
| Transformation Rules | 1,000+ built-in; cross-engine schema normalization supported |
| Retention Management | GDPR, HIPAA, PCI DSS, SOX retention schedules |
| Legal Hold | Instance and table-level hold orchestration with audit trail |
| Deployment | GCP (GCS Lakehouse) · On-premises · Multi-cloud |
| Security & Compliance | TLS 1.3 in transit · AES-256 at rest · WORM |
How It Works
Up and Running in 4 Steps
01
Connect to Cloud SQL
Authenticate via JDBC (Cloud SQL proxy or direct IP) to Cloud SQL for MySQL, PostgreSQL, or SQL Server. Archon auto-discovers all databases, schemas, tables, and audit structures.
02
Map & Configure
Define database and schema scope, engine-specific change capture strategy, and jurisdiction-specific retention schedules. Configure PII masking for GDPR compliance.
03
Validate & Preview
Run a dry-run against sample Cloud SQL tables. Quality report flags null primary keys, proxy connectivity issues, and schema anomalies before full extraction.
04
Archive & Monitor
Execute full extraction to GCS Lakehouse. Trusted timestamps applied per table. Data queryable via Archon Analyzer or BigQuery without Cloud SQL compute.FAQ
Common Questions About the Google Cloud SQL Connector
-
1. Does Archon support all three Cloud SQL engine variants: MySQL, PostgreSQL, and SQL Server?
Yes. Archon supports all three Cloud SQL engine variants with engine-specific extraction, schema normalization, and change capture applied automatically.
-
2. Can Archon satisfy retention obligations beyond Cloud SQL's 365-day backup limit?
Yes. Archon provides permanent, WORM-immutable archiving that satisfies GDPR, HIPAA, and SOX retention mandates spanning years, independently of Cloud SQL backup retention settings.
-
3. Does Archon use Cloud SQL Auth Proxy for secure connectivity?
Yes. Archon supports Cloud SQL Auth Proxy for secure, encrypted connectivity, as well as direct IP connections with SSL/TLS enforcement.
-
4. Is archived Cloud SQL data queryable without Cloud SQL instances?
Yes. Archon archives to open Parquet/Delta Lake on GCS, queryable via Archon Analyzer, BigQuery federated queries, or Apache Spark without Cloud SQL compute costs.
-
5. Can Archon archive Cloud SQL data across multiple GCP projects in a single job?
Yes. Archon supports multi-project Cloud SQL archiving with project-level separation and independent audit trails for each GCP project.
Ready to archive your Google Cloud SQL data and retire the dependency?
Talk to an Archon connector specialist at archondatastore.com. Free consultation, no commitment, reply within 24 hours.
