Google Cloud SQL
Supported
Relational databases
Catalog Cloud SQL for PostgreSQL, MySQL and SQL Server instances using the engine’s own JDBC driver.
Capabilities
| Capability | Support | Notes |
|---|---|---|
| Tables, views & columns | Supported | Pick the template of the underlying engine; Cloud SQL Auth Proxy is supported by pointing the URL to the proxy. |
| Keys, constraints & indexes | Supported | |
| Procedures & functions | Supported | |
| Data lineage | Supported | |
| Lineage from query history | Not available | |
| Business glossary links | Supported | |
| Data quality probes | Supported | |
| Data profiling | Supported | |
| Data classification | Supported | |
| Chat with your data | Supported |
Connection settings
Create the connection on the Blindata Agent from Settings > Agents > Connections with the connection wizard, choosing PostgreSQL, MySQL or Microsoft SQL Server in the technology step.
| Driver class | org.postgresql.Driver |
|---|---|
| JDBC URL | jdbc:postgresql://<instance-ip>:5432/postgres |
| Authentication |
Service principal (shared technical user) User principal (personal credentials, BYOC) Ephemeral credentials (asked at each run)
|
| Crawling strategy | SQL |
The driver is included in the Blindata Agent: no installation is needed. Driver properties can be added under Advanced settings in the connection wizard.
Prerequisites & permissions
- A Blindata Agent installed with network access to Google Cloud SQL.
- Same as the underlying engine: see the PostgreSQL , MySQL or SQL Server pages.
Set up metadata crawling
- Create the connection to Google Cloud SQL on the agent (see Connection settings) and use Test to verify it.
- Create or open the system that represents Google Cloud SQL in the catalog and link it to the connection.
- In the CRAWLING tab add a crawling job with strategy SQL.
- Run a TEST to check the number of extracted objects, then RUN or schedule the job.
The job options and the column aliases of every extraction query are described in the Generic JDBC reference.