Download Google Cloud Spanner
Author: h | 2025-04-24
Title: Google's cloud spanner 1 Google's Cloud Spanner 2 The beat launch of Cloud Spanner was declared today by Google and it is a new globally distributed database service for the purpose
Cloud Spanner API - Google Cloud
SQL best practices Modify data Modify data using the Google Cloud consoleModify data using the gcloud CLIModify data using mutationsCompare DML with mutationsModify data using batch write AI and machine learning Vector search Perform similarity vector search by finding the K-nearest neighborsChoose among vector distance functions to measure vector embeddings similarityFind approximate nearest neighbors, create vector indexes, and query vector embeddingsExport embeddings to Vertex AI Vector Search Warm up database before application launch Spanner Graph Product overview Set up and query Spanner Graph Insert, update, or delete data Migrate to Spanner Graph Spanner Graph reference for openCypher users Troubleshoot Spanner Graph Monitor Optimize and troubleshoot Troubleshoot latency Latency points in a Spanner requestIdentify where latency occursUse metrics to diagnose latencyCalculate streaming and partition request latencyIdentify transactions that cause high latencies Troubleshoot performance regressions Troubleshoot with request tags and transaction tags Troubleshoot deadline exceeded errors Troubleshoot Vertex AI integration errors Error codes Set up and query Spanner Graph Stay organized with collections Save and categorize content based on your preferences. This document shows you how to set up and query Spanner Graph usingthe Google Cloud console and client libraries.The following topics help you learn how:Create a Spanner instance.Create a database with a Spanner Graph schema.Insert graph data.Query the graph you created.Clean up resources.To learn about Spanner pricing details, seeSpanner pricing.To try out a codelab, see Getting started with Spanner Graph.Before you begin Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads. In the Google Cloud console, on the project selector page, select or create a Google Cloud project. Go to project selector Make sure that billing is enabled for your Google Cloud project. In the Google Cloud console, on the project selector page, select or create a Google Cloud project. Go to project selector Make sure that billing is enabled for your Google Cloud project. The Spanner API should be auto-enabled. If not, enable it manually: Enable Spanner API To get The permissions that you need to create instances and databases, ask your administrator to grant you the Cloud Spanner Admin (roles/spanner.admin) IAM role on your project. Create an instanceWhen you first use Spanner, you must create an instance, whichis an allocation of resources that are used by Spanner databases.This section shows you how to create an instance usingthe Google Cloud console.In the Google Cloud console, go to the Spanner page.Go to Spanner Select or create a Google Cloud project if you haven't done so already.Do one of the following:If you haven't created a Spanner instance before, on theWelcome to Spanner page, clickCreate a provisioned instance.If you've created a Spanner instance, on the Instancespage, click Create instance.On the Select an edition page, select Enterprise Plus orEnterprise.Spanner Graph is available only in the Enterprise edition orEnterprise Plus edition. To compare the different editions, clickCompare editions. For more information, see theSpanner editions overview.Click Continue.In Instance name, enter an instance name, for example,test-instance.In Instance ID keep or change the instance ID. Your instance ID defaultsto your instance name, but you can change it. Your instance name andinstance ID can be the same or they can be different.Click Continue.In Choose a configuration, do the following:Keep Regional selected.In Select a configuration, select a region. The region you select iswhere your instances are stored and replicated.Click Continue.In Configure compute capacity, do the following:In Select unit, select Processing units (PUs).In Choose a scaling mode, keep Manual allocation selected andin Quantity keep 1000 processing units.Click Create.The Google Cloud console displays the Overview page for theinstance you created.Create a database with Spanner Graph schemaThis section shows you how to use the Google Cloud console and client libraries tocreate a database with Spanner Graph schema. Console In the Google Cloud console, go to the SpannerInstances page.Go to Spanner instances Click the instance you created, for example, Test Instance.In Overview, under the name of your instance, click Createdatabase.In Database name, enter a database name. For example, example-db.In Select database dialect, choose Google Standard SQL.Spanner Graph isn't available in the PostgreSQL dialect. Yourdatabase creation page now looks like this: Copy and paste theGoogle Cloud Spanner - Anaconda.org
This page describes how to use the Dataflow connector forSpanner to import, export, and modify data in SpannerGoogleSQL-dialect databases and PostgreSQL-dialect databases.Dataflow is a managed service for transforming and enrichingdata. The Dataflow connector for Spanner lets you readdata from and write data to Spanner in a Dataflowpipeline, optionally transforming or modifying the data. You can also createpipelines that transfer data between Spanner and otherGoogle Cloud products.The Dataflow connector is the recommended method for efficientlymoving data into and out of Spanner in bulk. It's also therecommended method for performing large transformations to a database which arenot supported by Partitioned DML, such as table moves and bulk deletesthat require a JOIN. When working with individual databases, there are othermethods you can use to import and export data:Use the Google Cloud console to export an individual database fromSpanner to Cloud Storage in Avroformat.Use the Google Cloud console to import a database back intoSpanner from files you exported to Cloud Storage.Use the REST API or Google Cloud CLI to run export or importjobs from Spanner to Cloud Storage and back also usingAvro format.The Dataflow connector for Spanner is part of theApache Beam Java SDK, and it provides an API for performing the previousactions. For more information about some of the concepts discussed in this page,such as PCollection objects and transforms, see the Apache Beam programmingguide.Add the connector to your Maven projectTo add the Google Cloud Dataflow connector to a Mavenproject, add the beam-sdks-java-io-google-cloud-platform Maven artifact toyour pom.xml file as a dependency.For example, assuming that your pom.xml file sets beam.version to theappropriate version number, you would add the following dependency: org.apache.beam beam-sdks-java-io-google-cloud-platform ${beam.version}Read data from SpannerTo read from Spanner, apply the SpannerIO.readtransform. Configure the read using the methods in theSpannerIO.Read class. Applying the transform returns aPCollection, where each element in the collectionrepresents an individual row. Title: Google's cloud spanner 1 Google's Cloud Spanner 2 The beat launch of Cloud Spanner was declared today by Google and it is a new globally distributed database service for the purpose project_id = Your Google Cloud project ID instance_id = Your Spanner instance ID database_id = Your Spanner database ID require google/cloud/spanner spanner =Authenticate to Spanner - Google Cloud
Run a graph queryThis section shows you how to use the Google Cloud console or client librariesto run a Spanner Graph schema query. Console On the database Overview page, click Spanner Studio in thenavigation menu.On the Spanner Studio page, click New tab or use theeditor tab.Enter the following query in the query editor. The query finds everyonethat Dana transferred money to, and the amount of those transfers.GRAPH FinGraphMATCH (from_person:Person {name: "Dana"})-[:Owns]-> (from_account:Account)-[transfer:Transfers]-> (to_account:Account)-[:Owns]-(to_person:Person)RETURN from_person.name AS from_account_owner, from_account.id AS from_account_id, to_person.name AS to_account_owner, to_account.id AS to_account_id, transfer.amount AS amountClick Run.The Results tab displays the following paths from Dana throughAccount {id:20}:To Account {id:7} owned by Alex.To Account {id:16} owned by Lee. Client libraries Clean upMany of the examples in What's next make use of the resourcesthat you set up in this document. If you want to continue working withSpanner Graph using one of these examples, don't perform these cleanupsteps yet. This section shows you how to use the Google Cloud console to cleanup your resources.Otherwise, to avoid additional charges to your Cloud Billing account, deletethe database and the instance that you created during setup. Deleting aninstance automatically deletes all databases created in the instance.Delete the databaseIn the Google Cloud console, go to the Spanner Instances page.Go to Spanner instances Click the name of the instance that has the database that you want todelete, for example, Test Instance.Click the name of the database that you want to delete, for example,example-db.On the Database details page, click delete Delete database.Confirm that you want to delete the database by entering the databasename and clicking Delete.Delete the instanceIn Google Cloud console, go to the Spanner Instances page.Go to Spanner instances Click the name of the instance that you want to delete, for example,Test Instance.Click Delete instance.Confirm that you want to delete the instance by entering the instancename and clicking Delete.What's nextLearn more about Spanner Graph using a codelab.Learn about the Spanner Graph schema.Create, update, or drop a Spanner Graph schema.Insert, update, or delete Spanner Graph data.Spanner Graph queries overview.Migrate to Spanner Graph. Except as otherwise noted, the content of this page is licensed under the Creative Commons : 1 AlbumId : 1 AlbumTitle : Total JunkCleanupTo avoid incurring additional charges to your Cloud Billing account for theresources used in this tutorial, drop the database and delete the instance thatyou created.Delete the databaseIf you delete an instance, all databases within it are automatically deleted.This step shows how to delete a database without deleting an instance (you wouldstill incur charges for the instance).On the command linegcloud spanner databases delete example-db --instance=test-instanceUsing the Google Cloud consoleGo to the Spanner Instances page in the Google Cloud console.Go to the Instances page Click the instance.Click the database that you want to delete.In the Database details page, click Delete.Confirm that you want to delete the database and click Delete.Delete the instanceDeleting an instance automatically drops all databases created in that instance.On the command linegcloud spanner instances delete test-instanceUsing the Google Cloud consoleGo to the Spanner Instances page in the Google Cloud console.Go to the Instances page Click your instance.Click Delete.Confirm that you want to delete the instance and click Delete.Google Cloud Spanner C Client: Cloud Spanner C Client
In the next section.Setting up cross-cloud connectivity to SpannerEstablishing cross-cloud connectivity from a third-party cloud provider to Spanner is a straightforward process. The following section provides a step-by-step guide on setting up this connection.1. Physical connectivityThe first thing you will need to set up is a Virtual Private Cloud (VPC) network that you can connect to from other clouds. You can think of a VPC network as similar to a physical network, except that it is virtualized within Google Cloud. It consists of a list of regional virtual subnetworks (subnets) in data centers, all connected by a global wide area network. A VPC also enables you to privately connect networks outside of Google to Google Cloud products.(a) Set up VPC network using Google Cloud consoleSimilarly, you will need to have a VPC network on the other Cloud Provider into which to terminate connectivity.Next, you can connect your Google Cloud VPC network to your third-party public cloud environment through Cross-Cloud Interconnect. Go to the Interconnect console and choose Cross-Cloud Interconnect to order a new Cross-Cloud connection:(b) Set up Cross-Cloud Interconnect using Google Cloud consoleNext, you can choose the public cloud provider you’d like to connect to, along with the location and capacity.If you are using regional Spanner, then you should build the connection in the same location as the Spanner region to get the best latency. For multi-regional Spanner, we recommend setting up Interconnects in all the read-write and read-only regions. For example, if you use nam3 configuration, you can setCloud Spanner API - Class Google::Cloud::Spanner::Client (v2.24.0)
Spanner is a fully managed database service for both relational and non-relational workloads that offers strong consistency at global scale, high performance at virtually unlimited scale, and high availability with up to five 9s SLA. And as cross-cloud and hybrid cloud strategies gain traction, customers are increasingly seeking the flexibility to utilize Spanner's exceptional database capabilities while running their compute stack on a third-party cloud provider.Key considerations for such cross-cloud setups include:Latency: Customers want their application response times to be low for OLTP workloads.Security: With data traversing cloud boundaries and the sensitivity of information stored in Spanner, secure data transfer is paramount.Availability: Spanner boasts a high SLA, which our customers appreciate. The cross-cloud setup must similarly maintain a high SLA.Ease of setup: Establishing cross-cloud access that addresses the first three areas can be complex.Cost effectiveness: With data traffic flowing between clouds, the cross-cloud solution must be cost-effective.This blog explores how to use Google Cloud’s Cross-Cloud Interconnect to achieve the aforementioned goals.Cross-Cloud InterconnectIn the simplest model, applications can connect to Spanner at spanner.googleapis.com over the public internet. However, customers with increased reliability, latency, security and privacy requirements prefer to connect their workloads to their database environments privately.For application owners who leverage best-of-breed services from different public cloud providers, they need seamless, robust network connectivity across multiple environments. Google Cloud recently introduced Cross-Cloud Interconnect to its network connectivity portfolio to simplify the consumption of differentiated Google Cloud Services like Spanner, from different public cloud environments.Cross-Cloud Interconnect provides:Simplicity, as it does not require. Title: Google's cloud spanner 1 Google's Cloud Spanner 2 The beat launch of Cloud Spanner was declared today by Google and it is a new globally distributed database service for the purpose project_id = Your Google Cloud project ID instance_id = Your Spanner instance ID database_id = Your Spanner database ID require google/cloud/spanner spanner =Cloud Spanner support for Djangogoogle-cloud-spanner
Prepare your local C# environmentSet the GOOGLE_PROJECT_ID environment variable to your Google Cloud projectID.First, set GOOGLE_PROJECT_ID for the current PowerShell session:$env:GOOGLE_PROJECT_ID = "MY_PROJECT_ID"Then, set GOOGLE_PROJECT_ID for all processes created after thiscommand:[Environment]::SetEnvironmentVariable("GOOGLE_PROJECT_ID", "MY_PROJECT_ID", "User")Download credentials.Go to the Credentials page in the Google Cloud console.Go to the Credentials page Click Create credentials and choose Service account key.Under "Service account", choose Compute Engine default serviceaccount, and leave JSON selected under "Key type". ClickCreate. Your computer downloads a JSON file.Set up credentials. For a file named FILENAME.json in CURRENT_USER'sDownloads directory, located on the C drive, run the following commands toset GOOGLE_APPLICATION_CREDENTIALS to point to the JSON key:First, to set GOOGLE_APPLICATION_CREDENTIALS for this PowerShellsession:$env:GOOGLE_APPLICATION_CREDENTIALS = "C:\Users\CURRENT_USER\Downloads\FILENAME.json"Then, to set GOOGLE_APPLICATION_CREDENTIALS for all processes createdafter this command:[Environment]::SetEnvironmentVariable("GOOGLE_APPLICATION_CREDENTIALS", "C:\Users\CURRENT_USER\Downloads\FILENAME.json", "User")Clone the sample app repository to your local machine:git clone you can download thesampleas a zip file and extract it.Open Spanner.sln, located in the dotnet-docs-samples\spanner\apidirectory of the downloaded repository, with Visual Studio 2017 or later, thenbuild it.Change to the directory within the downloaded repository that contains thecompiled application. For example:cd dotnet-docs-samples\spanner\api\SpannerCreate an instanceWhen you first use Spanner, you must create an instance, which is anallocation of resources that are used by Spanner databases. When youcreate an instance, you choose an instance configuration, which determineswhere your data is stored, and also the number of nodes to use, which determinesthe amount of serving and storage resources in your instance.Execute the following command to create a Spanner instance in the regionus-central1 with 1 node:gcloud spanner instances create test-instance --config=regional-us-central1 ` --description="Test Instance" --nodes=1Note that this creates an instance with the following characteristics:Instance ID test-instanceDisplay name Test InstanceInstance configuration regional-us-central1 (Regional configurations storedata in one region, while multi-region configurations distribute data acrossmultiple regions. For more information, see About instances.)Node count of 1 (node_count corresponds to the amount of serving and storageresources available to databases in the instance. Learn more in Nodes andprocessing units.)You should see:Creating instance...done.Look through sample filesThe samples repository contains a sample that shows how to use Spannerwith C#.Take a look through the Spanner .NET GitHub repository,which shows how to create a database and modify a database schema. The data usestheComments
SQL best practices Modify data Modify data using the Google Cloud consoleModify data using the gcloud CLIModify data using mutationsCompare DML with mutationsModify data using batch write AI and machine learning Vector search Perform similarity vector search by finding the K-nearest neighborsChoose among vector distance functions to measure vector embeddings similarityFind approximate nearest neighbors, create vector indexes, and query vector embeddingsExport embeddings to Vertex AI Vector Search Warm up database before application launch Spanner Graph Product overview Set up and query Spanner Graph Insert, update, or delete data Migrate to Spanner Graph Spanner Graph reference for openCypher users Troubleshoot Spanner Graph Monitor Optimize and troubleshoot Troubleshoot latency Latency points in a Spanner requestIdentify where latency occursUse metrics to diagnose latencyCalculate streaming and partition request latencyIdentify transactions that cause high latencies Troubleshoot performance regressions Troubleshoot with request tags and transaction tags Troubleshoot deadline exceeded errors Troubleshoot Vertex AI integration errors Error codes Set up and query Spanner Graph Stay organized with collections Save and categorize content based on your preferences. This document shows you how to set up and query Spanner Graph usingthe Google Cloud console and client libraries.The following topics help you learn how:Create a Spanner instance.Create a database with a Spanner Graph schema.Insert graph data.Query the graph you created.Clean up resources.To learn about Spanner pricing details, seeSpanner pricing.To try out a codelab, see Getting started with Spanner Graph.Before you begin Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads. In the Google Cloud console, on the project selector page, select or create a Google Cloud project. Go to project selector Make sure that billing is enabled for your Google Cloud project. In the Google Cloud console, on the project selector page, select or create a Google Cloud project. Go to project selector Make sure that billing is enabled for your Google Cloud project. The Spanner API should be auto-enabled. If not, enable it manually: Enable Spanner API To get
2025-04-02The permissions that you need to create instances and databases, ask your administrator to grant you the Cloud Spanner Admin (roles/spanner.admin) IAM role on your project. Create an instanceWhen you first use Spanner, you must create an instance, whichis an allocation of resources that are used by Spanner databases.This section shows you how to create an instance usingthe Google Cloud console.In the Google Cloud console, go to the Spanner page.Go to Spanner Select or create a Google Cloud project if you haven't done so already.Do one of the following:If you haven't created a Spanner instance before, on theWelcome to Spanner page, clickCreate a provisioned instance.If you've created a Spanner instance, on the Instancespage, click Create instance.On the Select an edition page, select Enterprise Plus orEnterprise.Spanner Graph is available only in the Enterprise edition orEnterprise Plus edition. To compare the different editions, clickCompare editions. For more information, see theSpanner editions overview.Click Continue.In Instance name, enter an instance name, for example,test-instance.In Instance ID keep or change the instance ID. Your instance ID defaultsto your instance name, but you can change it. Your instance name andinstance ID can be the same or they can be different.Click Continue.In Choose a configuration, do the following:Keep Regional selected.In Select a configuration, select a region. The region you select iswhere your instances are stored and replicated.Click Continue.In Configure compute capacity, do the following:In Select unit, select Processing units (PUs).In Choose a scaling mode, keep Manual allocation selected andin Quantity keep 1000 processing units.Click Create.The Google Cloud console displays the Overview page for theinstance you created.Create a database with Spanner Graph schemaThis section shows you how to use the Google Cloud console and client libraries tocreate a database with Spanner Graph schema. Console In the Google Cloud console, go to the SpannerInstances page.Go to Spanner instances Click the instance you created, for example, Test Instance.In Overview, under the name of your instance, click Createdatabase.In Database name, enter a database name. For example, example-db.In Select database dialect, choose Google Standard SQL.Spanner Graph isn't available in the PostgreSQL dialect. Yourdatabase creation page now looks like this: Copy and paste the
2025-04-20This page describes how to use the Dataflow connector forSpanner to import, export, and modify data in SpannerGoogleSQL-dialect databases and PostgreSQL-dialect databases.Dataflow is a managed service for transforming and enrichingdata. The Dataflow connector for Spanner lets you readdata from and write data to Spanner in a Dataflowpipeline, optionally transforming or modifying the data. You can also createpipelines that transfer data between Spanner and otherGoogle Cloud products.The Dataflow connector is the recommended method for efficientlymoving data into and out of Spanner in bulk. It's also therecommended method for performing large transformations to a database which arenot supported by Partitioned DML, such as table moves and bulk deletesthat require a JOIN. When working with individual databases, there are othermethods you can use to import and export data:Use the Google Cloud console to export an individual database fromSpanner to Cloud Storage in Avroformat.Use the Google Cloud console to import a database back intoSpanner from files you exported to Cloud Storage.Use the REST API or Google Cloud CLI to run export or importjobs from Spanner to Cloud Storage and back also usingAvro format.The Dataflow connector for Spanner is part of theApache Beam Java SDK, and it provides an API for performing the previousactions. For more information about some of the concepts discussed in this page,such as PCollection objects and transforms, see the Apache Beam programmingguide.Add the connector to your Maven projectTo add the Google Cloud Dataflow connector to a Mavenproject, add the beam-sdks-java-io-google-cloud-platform Maven artifact toyour pom.xml file as a dependency.For example, assuming that your pom.xml file sets beam.version to theappropriate version number, you would add the following dependency: org.apache.beam beam-sdks-java-io-google-cloud-platform ${beam.version}Read data from SpannerTo read from Spanner, apply the SpannerIO.readtransform. Configure the read using the methods in theSpannerIO.Read class. Applying the transform returns aPCollection, where each element in the collectionrepresents an individual row
2025-04-23Run a graph queryThis section shows you how to use the Google Cloud console or client librariesto run a Spanner Graph schema query. Console On the database Overview page, click Spanner Studio in thenavigation menu.On the Spanner Studio page, click New tab or use theeditor tab.Enter the following query in the query editor. The query finds everyonethat Dana transferred money to, and the amount of those transfers.GRAPH FinGraphMATCH (from_person:Person {name: "Dana"})-[:Owns]-> (from_account:Account)-[transfer:Transfers]-> (to_account:Account)-[:Owns]-(to_person:Person)RETURN from_person.name AS from_account_owner, from_account.id AS from_account_id, to_person.name AS to_account_owner, to_account.id AS to_account_id, transfer.amount AS amountClick Run.The Results tab displays the following paths from Dana throughAccount {id:20}:To Account {id:7} owned by Alex.To Account {id:16} owned by Lee. Client libraries Clean upMany of the examples in What's next make use of the resourcesthat you set up in this document. If you want to continue working withSpanner Graph using one of these examples, don't perform these cleanupsteps yet. This section shows you how to use the Google Cloud console to cleanup your resources.Otherwise, to avoid additional charges to your Cloud Billing account, deletethe database and the instance that you created during setup. Deleting aninstance automatically deletes all databases created in the instance.Delete the databaseIn the Google Cloud console, go to the Spanner Instances page.Go to Spanner instances Click the name of the instance that has the database that you want todelete, for example, Test Instance.Click the name of the database that you want to delete, for example,example-db.On the Database details page, click delete Delete database.Confirm that you want to delete the database by entering the databasename and clicking Delete.Delete the instanceIn Google Cloud console, go to the Spanner Instances page.Go to Spanner instances Click the name of the instance that you want to delete, for example,Test Instance.Click Delete instance.Confirm that you want to delete the instance by entering the instancename and clicking Delete.What's nextLearn more about Spanner Graph using a codelab.Learn about the Spanner Graph schema.Create, update, or drop a Spanner Graph schema.Insert, update, or delete Spanner Graph data.Spanner Graph queries overview.Migrate to Spanner Graph. Except as otherwise noted, the content of this page is licensed under the Creative Commons
2025-04-23: 1 AlbumId : 1 AlbumTitle : Total JunkCleanupTo avoid incurring additional charges to your Cloud Billing account for theresources used in this tutorial, drop the database and delete the instance thatyou created.Delete the databaseIf you delete an instance, all databases within it are automatically deleted.This step shows how to delete a database without deleting an instance (you wouldstill incur charges for the instance).On the command linegcloud spanner databases delete example-db --instance=test-instanceUsing the Google Cloud consoleGo to the Spanner Instances page in the Google Cloud console.Go to the Instances page Click the instance.Click the database that you want to delete.In the Database details page, click Delete.Confirm that you want to delete the database and click Delete.Delete the instanceDeleting an instance automatically drops all databases created in that instance.On the command linegcloud spanner instances delete test-instanceUsing the Google Cloud consoleGo to the Spanner Instances page in the Google Cloud console.Go to the Instances page Click your instance.Click Delete.Confirm that you want to delete the instance and click Delete.
2025-03-31In the next section.Setting up cross-cloud connectivity to SpannerEstablishing cross-cloud connectivity from a third-party cloud provider to Spanner is a straightforward process. The following section provides a step-by-step guide on setting up this connection.1. Physical connectivityThe first thing you will need to set up is a Virtual Private Cloud (VPC) network that you can connect to from other clouds. You can think of a VPC network as similar to a physical network, except that it is virtualized within Google Cloud. It consists of a list of regional virtual subnetworks (subnets) in data centers, all connected by a global wide area network. A VPC also enables you to privately connect networks outside of Google to Google Cloud products.(a) Set up VPC network using Google Cloud consoleSimilarly, you will need to have a VPC network on the other Cloud Provider into which to terminate connectivity.Next, you can connect your Google Cloud VPC network to your third-party public cloud environment through Cross-Cloud Interconnect. Go to the Interconnect console and choose Cross-Cloud Interconnect to order a new Cross-Cloud connection:(b) Set up Cross-Cloud Interconnect using Google Cloud consoleNext, you can choose the public cloud provider you’d like to connect to, along with the location and capacity.If you are using regional Spanner, then you should build the connection in the same location as the Spanner region to get the best latency. For multi-regional Spanner, we recommend setting up Interconnects in all the read-write and read-only regions. For example, if you use nam3 configuration, you can set
2025-04-23