Skip to content

CloudSQL Connector

The CloudSQL Connector enables seamless migration of legacy databases (Oracle, SQL Server) to Google Cloud's CloudSQL for PostgreSQL. It automates schema conversion, data transfer, and workload remediation with support for VPC-native networking and enterprise-grade security.

Architecture

Prerequisites & Configuration

QMigrator must be installed.

Before proceeding, ensure you have:

  • Valid project details and login credentials from Quadrant
  • Database connection details and access credentials for source and target systems
  • Network reachability confirmed between QMigrator and your database environments
  • Appropriate permissions configured (see below)

Required Permissions

QMigrator reads data from one or more tables across different schemas and migrates them to target databases.

Create a dedicated QMigrator user account with a strong, unique password. The QMigrator account must have:

  • Schema Creation & Admin Access: Ability to create schemas and full admin access to all tables within that schema (including creating, deleting, and read/write operations)
  • Read-only Access: Read-only access to any tables and views in any schema that QMigrator needs to access
  • Read-write Access: If loading service data into your warehouse, read-write access to the schema where QMigrator loads data

Network Configuration

QMigrator can connect to CloudSQL instances using various networking controls.

Allowed IP Addresses

Add QMigrator's public IP addresses to your firewall and/or configure your pg_hba.conf file to allow only the QMigrator user to connect.

To get QMigrator IP address: Use your GKE cluster with NAT Gateway to retrieve the public IP address.

Connecting Within VPC

Create the GKE cluster in the same network using a VPC-native cluster. This enables connection to CloudSQL within the same network using Private Service Access.

Connection Setup in QMigrator

  1. Click on the Setup menu and navigate to the Connections screen
  2. Select Database as the migration source to create the source connection

  3. In the Connection Type field, choose your target database type
    Connection

  4. Provide the CloudSQL connection details - see table below

  5. Click Test connection to verify connectivity
    Connection

CloudSQL Connection Parameters

Parameter Description Example
Connection Name A reference name for the target connection TGT_CloudSQL
Hostname/IP The host or IP of the target database 10.89.*.*
Port Port for the database connection 5432
Service Name The service name for CloudSQL databases target_db
DB Name The name of the target database target_db
Schema The schema containing tables to migrate public
Username Username for target database authentication db_user
Password Password for authentication ****

Data Migration

Migration Steps

  1. Select the DAG execution file in the Execution tab
  2. Select the DAG (table) from the list to be migrated
  3. Optionally schedule the DAG for a future date/time by clicking Schedule DAG
  4. Start execution immediately by clicking Trigger DAG
    Migration

Migration Operations

Upon data migration start, QMigrator performs:
Migration

  • Validation checks
  • Table migration
  • Constraint deployment

Verification

After data migration completes, verify that table data is successfully available in the destination by manually checking the target database.
Migration