Cloud SQL for SQL Server error messages

• The username (or password) is incorrect.
• The user is connecting from a URL other than @XXX.
• The user doesn't have the correct privileges for the database they're trying to connect to.

Try these things ...

• Verify the username and corresponding password.
• Check the origin of the connection to see if it matches the URL where the user has access privileges.
• Check the user's grant privileges in the database.

You need to modify the private connection. Use the following command, and make sure to use the --force argument:

gcloud services vpc-peerings update \
--network=VPC_NETWORK \
--ranges=ALLOCATED_RANGES \
--service=servicenetworking.googleapis.com \
--force

For Illegal Argument, check the request to make sure each argument is permissible and each value for the argument is valid. For all other causes, check the log files to see if there is more information there.

You need to modify the private connection. Use the following command, and make sure to use the --force argument:

gcloud services vpc-peerings update \
--network=VPC_NETWORK \
--ranges=ALLOCATED_RANGES \
--service=servicenetworking.googleapis.com \
--force

Remove all Authorized Networks entries from the Cloud SQL instance if you can. Otherwise, create a replica without any Authorized Networks entries.

Use the sp_helpdb command to get information about the database.

Consider the following solutions:

• Manually expand the disk space or reduce the data in the database.
• Ensure that Automatic storage increase is enabled for the database instance.
• Add more filegroups and move data into them.
• Ensure that growth is not limited. Use the ALTER DATABASE command to enable autogrowth, if it is not already enabled, and to increase the maximum file size.
• Manage tempdb files. Use the DBCC OPENTRAN and DBCC SQLPERFcommands to check for open transactions that can cause the tempdb file or the transaction log to grow.

Edit the primary instance to upgrade it to a larger disk size.

Couldn't find free blocks in allocated IP ranges. Please allocate new ranges for this service provider.

There are no more available addresses in the allocated IP range.

Consider these possible scenarios:

• The size of the allocated IP range for the private service connection is smaller than /24.
• The size of the allocated IP range for the private service connection is too small for the number of Cloud SQL instances.
• The requirement on the size of allocated IP range will be larger if instances are created in multiple regions. See allocated range size

For each of the above scenarios, you can elect to either expand the existing or allocate an additional IP range to the private service connection.

If you're allocating a new range, take care to not create an allocation that overlaps with any existing allocations.

After creating a new IP range, update the VPC peering with the following command:

gcloud services vpc-peerings update \
--service=servicenetworking.googleapis.com
--ranges=OLD_RESERVED_RANGE_NAME,NEW_RESERVED_RANGE_NAME \
--network=VPC_NETWORK
--project=PROJECT_ID \
--force

If you're expanding an existing allocation, take care to only increase the allocation range and not decrease it. For example, if the original allocation was 10.0.10.0/24, make the new allocation at least 10.0.10.0/23.

In general, if starting from a /24 allocation, decrementing the /mask by 1 for each condition (additional instance type group, additional region) is a good rule of thumb. For example, if trying to create both instance type groups on the same allocation, going from /24 to /23 is enough.

After expanding an existing IP range, update the vpc peering with following command:

gcloud services vpc-peerings update \
--service=servicenetworking.googleapis.com
--ranges=RESERVED_RANGE_NAME \
--network=VPC_NETWORK \
--project=PROJECT_ID \
--force

Connecting from Cloud Shell to an instance with only a private IP address isn't currently supported.

To repair service permissions, disable the Service Networking API, wait five minutes and then re-enable it.

Enable the Service Networking API in your project. If you see this error when you're trying to assign a private IP address to a Cloud SQL instance, and you're using a Shared VPC, you also need to enable the Service Networking API for the host project.

Enable the Service Networking API in your project. If you see this error when you're trying to assign a private IP address to a Cloud SQL instance, and you're using a Shared VPC, you also need to enable the Service Networking API for the host project.

Wait for the previous operation to finish before beginning another.

Edit the target instance to increase its storage size.

Request an increase to your quotas from the Google Cloud console.

Verify that you have a valid service account key JSON file in the location stored in the GOOGLE_APPLICATION_CREDENTIALS environment variable and that the variable points to the correct location.

Create a new server certificate and rotate.

• The user might not have all the Cloud Storage permissions it needs.
• The database table might not exist.

Try these things ...

• Check that you have at least WRITER permissions on the bucket and READER permissions on the export file. For more information on configuring access control in Cloud Storage, see Create and Manage Access Control Lists
• Ensure the table exists. If the table does exist, confirm that you have the correct permissions on the storage bucket.

The dump transaction can fail if you use the following statements during the export operation:

• ALTER TABLE
• CREATE TABLE
• DROP TABLE
• RENAME TABLE
• TRUNCATE TABLE

Remove any of these statements from the dump operation.

Increase the temp_file_limit size. See Configuring database flags.

• At the database level, the database user must exist and its password match
• At the project level, the user might not have the correct IAM permissions, including the serviceusage.services.use or cloudsql.instances.connect permissions.
• At the network level, if the Cloud SQL instance is using public IP the connection's source IP must be in an authorized network.

Try these things ...

• Ensure the user exists and its password matches.
• Assign the Service Usage Consumer role to the user account. This role includes the permission serviceusage.services.use.
• If using public IP, ensure the source IP is in an authorized network.

Until fixed, see this discussion on GitHub, which includes a workaround.

• This can occur when you are trying to re-use the same name as a recently-deleted instance.
• It can also be caused by intermittent connectivity issues.
• The logs might show that the Service Networking API is not enabled for the project.
• The error has also been seen when trying to create multiple instances in parallel. For example, Terraform scripts make this attempt possible.
• Another cause can be that a specific resource is exhausted or a quota limit has been exceeded. Look in the logs for an entry like Quota 'INTERNAL_FORWARDING_RULES_WITH_TARGET_INSTANCE_PER_NETWORK' exceeded. Limit: 100.0 globally
• This error can occur if subnet creation fails when there are no more available addresses in the IP range.

• Instance names cannot be re-used until about a week after deletion.
• In the case of intermittent connectivity issues, the only remedy is to try again.
• Enable the Service Networking API for the project.
• Parallel instance creation scripts will only succeed in creating one of the instances. Modify the script to wait until each instance create operation is complete before continuing to the next one.
• Allocate new ranges.