Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/sql/docs/sqlserver/connect-run below:

Connect from Cloud Run | Cloud SQL for SQL Server

Stay organized with collections Save and categorize content based on your preferences.

This page contains information and examples for connecting to a Cloud SQL instance from a service running in Cloud Run.

For step-by-step instructions on running a Cloud Run sample web application connected to Cloud SQL, see the quickstart for connecting from Cloud Run.

Cloud SQL is a fully-managed database service that helps you set up, maintain, manage, and administer your relational databases in the cloud.

Cloud Run is a managed compute platform that lets you run containers directly on top of Google Cloud infrastructure.

1. Enable the Cloud SQL Admin API in the Google Cloud project that you are connecting from, if you haven't already done so:

   Enable the API

2. Create a Cloud SQL for SQL Server instance. We recommend that you choose a Cloud SQL instance location in the same region as your Cloud Run service for better latency, to avoid some networking costs, and to reduce cross region failure risks.

   By default, Cloud SQL assigns a public IP address to a new instance. You also have the option to assign a private IP address. For more information about the connectivity options for both, see the Connecting Overview page.

3. When you create the instance, you can choose the server certificate (CA) hierarchy for the instance and then configure the hierarchy as the serverCaMode for the instance. You must select the per-instance CA option (GOOGLE_MANAGED_INTERNAL_CA) as the server CA mode for instances that you want to connect to from web applications.

The steps to configure Cloud Run depend on the type of IP address that you assigned to your Cloud SQL instance. If you route all egress traffic through Direct VPC egress or a Serverless VPC Access connector, use a private IP address.

.

Cloud Run supports connecting to Cloud SQL for SQL Server over public IP using the Go, Java and Python connectors.

• Make sure that the instance has a public IP address. You can verify this on the Overview page for your instance in the Google Cloud console. If you need to add one, see the Configuring public IP page for instructions.
• Get the INSTANCE_CONNECTION_NAME for your instance. You can find this value on the Overview page for your instance in the Google Cloud console or by running the following gcloud sql instances describe command:

  gcloud sql instances describe INSTANCE_NAME
     

  Replace INSTANCE_NAME with the name of your Cloud SQL instance.
• Get the CLOUD_RUN_SERVICE_ACCOUNT_NAME for your Cloud Run service. You can find this value on the IAM page of the project that's hosting the Cloud Run service in the Google Cloud console or by running the following gcloud run services describe command in the project that's hosting the Cloud Run service:

  gcloud run services describe CLOUD_RUN_SERVICE_NAME
  --region CLOUD_RUN_SERVICE_REGION --format="value(spec.template.spec.serviceAccountName)"
     

  Replace the following variables:
  • CLOUD_RUN_SERVICE_NAME: the name of your Cloud Run service
  • CLOUD_RUN_SERVICE_REGION: the region of your Cloud Run service
• Configure the service account for your Cloud Run service. To connect to Cloud SQL, make sure that the service account has the Cloud SQL Client IAM role.
Note: If the authorizing service account belongs to a different project than the one containing the Cloud SQL instance, you must
• Enable the Cloud SQL Admin API in both the projects.
• Add the IAM permissions for the service account in the project containing the Cloud SQL instance.
• If you're adding a Cloud SQL connection to a new service, you need to have your service containerized and uploaded to the Container Registry or Artifact Registry. If you don't already have a connection, then see these instructions about building and deploying a container image.

• If you're connecting to instances that are configured with the shared certificate authority (CA) (GOOGLE_MANAGED_CAS_CA) option or the customer-managed CA (CUSTOMER_MANAGED_CAS_CA) option as the server CA mode, then select the second generation execution environment when you select the execution environment for the service. Both server CA mode options require you to connect to the instance with the Cloud SQL Auth Proxy v2.

  If your service runs in a first generation execution environment, then you can connect only to Cloud SQL instances that are configured with the per-instance certificate authority (CA) option (GOOGLE_MANAGED_INTERNAL_CA) as the server CA mode. The first generation execution environment of Cloud Run embeds the Cloud SQL Auth Proxy v1. For more information about connection requirements to Cloud SQL for the Cloud SQL Auth Proxy, see Requirements for using the Cloud SQL Auth Proxy.

Like any configuration change, setting a new configuration for the Cloud SQL connection leads to the creation of a new Cloud Run revision. Subsequent revisions will also automatically get this Cloud SQL connection unless you make explicit updates to change it.

1. Go to Cloud Run

2. Start configuring the service. To add Cloud SQL connections to an existing service, do the following:

   1. From the Services list, click the service name you want.
   2. Click Edit & deploy new revision.
3. Enable connecting to a Cloud SQL instance: Note: If your application is written in Java you can skip this step, since you do this in the Java Cloud SQL Connector.
   1. Click Container(s) and then Settings.
   2. Scroll to Cloud SQL connections.
   3. Click Add connection.
   4. Click Enable the Cloud SQL Admin button if you haven't enabled the Cloud SQL Admin API yet.
   • If you're adding a connection to a Cloud SQL instance in your project, then select the Cloud SQL instance you want from the menu.
   • If you're using a Cloud SQL instance from another project, then select custom connection string in the menu and enter the full instance connection name in the format PROJECT-ID:REGION:INSTANCE-ID.
   • To delete a connection, hold your cursor to the right of the connection to display the delete Delete icon, and click it.
   Note: For more information about adding Cloud SQL connections to a service that you're creating, see Deploying a new service.

4. Click Create or Deploy.

Before using any of the following commands, make the following replacements:

• IMAGE with the image you're deploying
• SERVICE_NAME with the name of your Cloud Run service

• INSTANCE_CONNECTION_NAME with the instance connection name of your Cloud SQL instance, or a comma delimited list of connection names.

  If you're deploying a new container, use the following command:

  gcloud run deploy \
    --image=IMAGE \
    --add-cloudsql-instances=INSTANCE_CONNECTION_NAME

  If you're updating an existing service, use the following command:

  gcloud run services update SERVICE_NAME \
    --add-cloudsql-instances=INSTANCE_CONNECTION_NAME

The following code creates a base Cloud Run container, with a connected Cloud SQL instance.

1. Apply the changes by entering terraform apply.
2. Verify the changes by checking the Cloud Run service, clicking the Revisions tab, and then the Connections tab.

If the authorizing service account belongs to a different project than the one containing the Cloud SQL instance, do the following:

• In both projects, enable the Cloud SQL Admin API.
• For the service account in the project that contains the Cloud SQL instance, add the IAM permissions.

1. Make sure that the Cloud SQL instance created previously has a private IP address. To add an internal IP address, see Configure private IP.
2. Configure your egress method to connect to the same VPC network as your Cloud SQL instance. Note the following conditions:
• Direct VPC egress and Serverless VPC Access both support communication to VPC networks connected using Cloud VPN and VPC Network Peering.
• Direct VPC egress and Serverless VPC Access don't support legacy networks.
• Unless you're using Shared VPC, a connector must share the same project and region as the resource that uses it, although the connector can send traffic to resources in different regions.
3. Connect using your instance's private IP address and port 1433.

After you configure Cloud Run, you can connect to your Cloud SQL instance.

For public IP paths, Cloud Run provides encryption and connects using the Cloud SQL connectors.

The Cloud SQL connectors are language specific libraries that provide encryption and IAM-based authorization when connecting to a Cloud SQL instance.

To see this snippet in the context of a web application, view the README on GitHub.

To see this snippet in the context of a web application, view the README on GitHub.

Note:

• CLOUD_SQL_CONNECTION_NAME should be represented as <MY-PROJECT>:<INSTANCE-REGION>:<INSTANCE-NAME>
• See the JDBC socket factory version requirements for the pom.xml file here .

To see this snippet in the context of a web application, view the README on GitHub.

To see this snippet in the context of a web application, view the README on GitHub.

Google recommends that you use Secret Manager to store sensitive information such as SQL credentials. You can pass secrets as environment variables or mount as a volume with Cloud Run.

After creating a secret in Secret Manager, update an existing service, with the following command:

gcloud run services update SERVICE_NAME \
  --add-cloudsql-instances=INSTANCE_CONNECTION_NAME
  --update-env-vars=INSTANCE_CONNECTION_NAME=INSTANCE_CONNECTION_NAME_SECRET \
  --update-secrets=DB_USER=DB_USER_SECRET:latest \
  --update-secrets=DB_PASS=DB_PASS_SECRET:latest \
  --update-secrets=DB_NAME=DB_NAME_SECRET:latest

The following creates secret resources to securely hold the database user, password, and name values using google_secret_manager_secret and google_secret_manager_secret_version. Note that you must update the project compute service account to have access to each secret.

Update the main Cloud Run resource to include the new secrets.

Apply the changes by entering terraform apply.

The example command uses the secret version, latest; however, Google recommends pinning the secret to a specific version, SECRET_NAME:v1.

For private IP paths, your application connects directly to your instance through a VPC network. This method uses TCP to connect directly to the Cloud SQL instance without using the Cloud SQL Auth Proxy.

Connect using the private IP address of your Cloud SQL instance as the host and port 1433.

You can use the Cloud SQL Auth Proxy when testing your application locally. See the quickstart for using the Cloud SQL Auth Proxy for detailed instructions.

You can also test using the Cloud SQL Proxy via a docker container.

Connections to underlying databases may be dropped, either by the database server itself, or by the platform infrastructure. We recommend using a client library that supports connection pools that automatically reconnect broken client connections. You can use Managed Connection Pooling with your Cloud SQL instances, which lets you scale your workloads by optimizing resource utilization and connection latency for your Cloud SQL instances using pooling. For detailed information about Managed Connection Pooling, see Managed Connection Pooling overview.

For more detailed examples on how to use connection pools, see the

page.

Both the MySQL and PostgreSQL editions of Cloud SQL impose a maximum limit on concurrent connections, and these limits may vary depending on the database engine chosen (see the

page).

Cloud Run container instances are limited to 100 connections to a Cloud SQL database. Each instance of a Cloud Run service or job can have 100 connections to the database, and as this service or job scales, the total number of connections per deployment can grow.

You can limit the maximum number of connections used per instance by using a connection pool. For more detailed examples on how to limit the number of connections, see the Managing database connections page.

Cloud Run provides a mechanism that connects using the Cloud SQL Auth Proxy, which uses the Cloud SQL Admin API.

apply to the Cloud SQL Auth Proxy. The Cloud SQL Admin API quota used is approximately two times the number of Cloud SQL instances configured by the number of Cloud Run instances of a particular service deployed at any one time. You can

to modify the expected API quota consumed.

• Learn more about Cloud Run.
• Learn more about building and deploying container images.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-14 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4