Google Cloud Spanner

Google Cloud Spanner

  • Verified Versions: Latest
  • Maintainer: Redgate

Supported Versions and Support Levels


Item Details
URL format jdbc:cloudspanner:/projects/project_name/instances/instance_name/databases/database_name?credentials=path/to/keyfile.json
Connecting to an emulator:
SSL support Yes
Ships with Flyway Command-line Yes
Maven Central coordinates
Supported versions 2.2.6 and later
Default Java class


Executing multiple schema changes against Cloud Spanner is comparatively slow due to its need to validate your data. You can read more about it here.

Flyway alleviates this via batching which executes multiple schema changes in one request to minimize latency and improve performance.

To enable batching follow the guide here for your platform.

In the Flyway Command-Line this would look like the following:

> flyway migrate -batch=true

Data limit

Flyway Community Edition has a 10GB limit on database size, and this is unlimited in Flyway Teams and Enterprise.

You can find out more about Flyway Teams Edition here.

Using Flyway with Google Cloud Spanner


  • Using Flyway with Maven?
    • Include the latest Flyway GCP Spanner dependency here in your pom
  • Using Flyway with Gradle?
    • Include the latest Flyway GCP Spanner dependency here as a buildscript dependency

Configuring Flyway

You must configure a JDBC URL that points to your database. You can configure a connection using this sample URL as an example:


We need to fetch three things to complete this url:

  • project_name
  • instance_name
  • database_name
  • A path to a keyfile.json for authentication (not required when connected to an emulated session)

project_name, instance_name, database_name can all be found on the Cloud Spanner web interface. For authentication, we recommend using the 'keyfile'. This requires creating a service account for Cloud Spanner.

To do this, open IAM within GCP project settings. There you can create a service account. Upon creating this you'll have the option to download the keyfile.

The authentication file needs to be accessible to Flyway, so save it somewhere accessible on your machine. Then configure path_to_service_account to point to this file.

You can learn more about service accounts here.

Set this URL in the url property in your Flyway configuration.

Other configuration

Set the user and password properties to empty in your Flyway configuration (conf or toml) since we're authenticating using the JDBC URL

Didn't find what you were looking for?