Cloud SQL

  1. 107 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Bug: Cannot create instance with the same name as instance deleted before

    1. Create Cloud SQL instance via gcloud command

    $ gcloud sql instances create sample-instance --database-version MYSQL56 --region asia-east1

    1. Delete Cloud SQL instance created above (== sample-instance) from Web UI

    2. Create Cloud SQL instance with the same name as instance created on step 1.

    $ gcloud sql instances create sample-instance --database-version MYSQL56 --region asia-east1

    1. Following error message is shown

    DEBUG: operation : None
    DEBUG: (gcloud.sql.instances.create) The instance or operation is not in an appropriate state to handle the request.
    Traceback (most recent call last):
    File "/usr/bin/../lib/google-cloud-sdk/./lib/googlecloudsdk/calliope/cli.py", line 591, in Execute
    result = args.cmdfunc(cli=self, args=args)
    File "/usr/bin/../lib/google-cloud-sdk/./lib/googlecloudsdk/calliope/backend.py", line

    101 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    36 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Auto-whitelist IPs from Instance Group for SQL access.

    It would be great to have an option under SQL -> instance details -> access control -> authorization to automatically allow connections from all VMs in a compute engine Instance Group.

    Right now only explicit IP/ranges can be whitelisted, which makes autohealing/scaling somewhat less automatic, or "Cloud SQL proxy" which is pretty convoluted.

    If there's already a way to do this, it doesn't seem intuitive.
    Thanks :)

    81 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Managed Upgrade for Postgres Instances

    With Postgres 9.6 EOL on the horizon (November 11, 2021), we need to start thinking about our upgrade process to get on the latest version of Postgres. The main reason we use Cloud SQL is that we do not have expertise in DB administration, so we are worried about this upgrade process.

    Unfortunately, Cloud SQL does not support managed upgrades of instance. It would be great if Cloud SQL could manage this for us by leveraging pg_upgrade (a la RDS).

    57 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Postgresql JDBC Connections from Google Apps Script

    Please 1) get Postgresql on Google Cloud out of Beta and 2) Support JDBC Connections from Google Apps Script

    43 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Create automated backups that are not stored on the instance

    Cloud SQL automated backups are now stored on the instance itself. So, if the instance is gone or deleted, the backups are as well.

    I know we can export the database to a bucket, but we cannot do this automatically. Only manually.

    What good is a backup if it gets deleted when I delete the instance, the idea of a backup is to restore something especially for when someone accidentally deletes the instance.

    This is even more important because deleting an instances is appearantly really easy to do. There is no 2FA or password asked.

    So, in short, I would…

    34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Pay-Per-Usage Scalable SQL Service

    The current pricing schemes allows for either pay-per-usage Datastore or BigQuery, or pay-per-machine fully transactional relational Database. What I would want is a scalable pay-per-usage service for SQL, where I dont have to pre-provision servers, but just have a fast and reliable SQL service where I get billed per used CPU cycles / RAM / Network / Storage at the end of the month. Currently, our SQL servers idle outside of standard business hours, and we have to over-provision for some rare complex queries.
    As you are anyway starting to make Cloud Spanner SQL compatible and have full control over…

    22 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. CloudSQL Multi-Master Replication

    The ability to create multi-master replication across different zones. We're looking to expand our MySQL scaling.

    Even giving us access to SUPER to manage our own replication chains would be helpful. There's no simple way to get failover options in different zones at the moment

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. TimescaleDB extension support

    On the issue tracker this is the top #1 feature request: https://issuetracker.google.com/issues/64602105

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Implement Database Level Backup

    The automated instance level backups are great! However, in my experience it is more common to restore a single database rather than an entire database server instance.

    At present, database restores from instance backups are time-consuming and tedious. This is an issue because often restores are highly time-critical and is beneficial to streamline the process so that a restored database can be operational as soon as possible.

    For example, the steps required might look like the following:
    1. Clone SQL server instance to a new instance so that other databases are not overwritten by the backup.
    2. Restore backup to…

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Update MySQL 8 minor version to MySQL 8.0.21

    It would be nice if the recently announced Cloud SQL version of MySQL 8 (currently 8.0.18) would be updated to the latest minor version 8.0.21. In 8.0.18, I'm experiencing a bug using a select statement joining two grouped statements with rollup that does not occur on 5.7 or 8.0.21.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Ability to immediate use a deleted cloudasql database

    Currently need to wait 24 hours before re-using a database instance name. Request the ability to override this setting and immediately reuse a database instance name.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Postgres smaller Read Replicas

    Today, when you create a replica for postgres in CloudSQL, it only allows VMs the same size of the master.

    It is very expensive this setup, at least for my team. We use the replica for reports that we do not want to impact the load of the master.

    I think it is a common case, on AWS it works fine.

    It seems to have a validation before doing anything on it. Maybe remove the validation, and show a disclaimer saying "at your own risk". I'm assuming it works behind the scenes.

    Or make it possible to create external replicas…

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Creating read replica even if first backup is not done yet

    I want to create read replica even there is no backup on master yet.

    I suggest some ways to implement:

    1. Create backup when user create read replica

    2. Reserve to create read replica when first backup is created

    3. Add option to create backup when user create instance
      $ gcloud sql instances create master --create-backup-immediately # other options...

    4. Allow users to create backup manually

    I appreciate if this feature is implemented.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow placing a lien on a cloud SQL database

    When you use tools like Terraform, one could imagine that due to a bug or error, a cloud sql database instance is removed.

    One way to prevent this from happening is to introduce liens for cloud SQL. That way Terraform's plan would suggest removing the cloud database, but the operation would simply fail because of the lien.

    Liens are now active on both project level, and compute instance level. I think applying this same concept to cloud SQL should not be too difficult and would really help.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. postgis 3.1.0

    I wanted to use STSquareGrid and STHexagonGrid earlier today. maybe I'll have to spin up pg in ComputeEngine until postgis 3.1.0 is supported in CloudSQL

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. gcloud sql connect --tunnel-through-iap

    gcloud sql connect should get an option --tunnel-through-iap much like gcloud compute ssh already has.

    Ie, it should be easy as a developer to connect to an instance regardless of local IP. And importantly, this should work also for instances on private ip/service networking.

    While it is curently possible to accomplish something like this using:

    gcloud compute ssh BASTIONVM --tunnel-through-iap -- PGPASSWORD=$(gcloud auth print-access-token) PGUSER=$(gcloud config list account --format "value(core.account)") PGHOST=CLOUDSQLDNSEDHOSTNAMEORIP psql NAMEOF_DB

    it is kind of cumbersome and there is a bastion VM that needs to be maintained.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Enable X Plugin in MySQL

    Enable the X plugin in MySQL and allow clients to connect to MySQL using the X Dev API.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Support CDC for SQL Server databases

    I would liek CDC running for several reasons in user databases, but this seems not supported. I did a quick test like below:

    CREATE DATABASE dummyDB;
    GO

    USE dummyDB;
    GO
    EXEC sys.spcdcenable_db;

    Output:
    Msg 22902, Level 16, State 1, Procedure sys.spcdcenable_db, Line 20 [Batch Start Line 5]
    Caller is not authorized to initiate the requested action. Sysadmin privileges are required.

    Also tried to import a database (with cdc on) backup, and the import fails.

    This is not included in the list of features not supported, and I think that it should. https://cloud.google.com/sql/docs/sqlserver/features#sqlserver-unavailable

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. Instance collation configurable for SQL Server

    Haven´t found a way to edit the collation for the whole instance on SQL Server. I have seen the default one is SQLLatin1GeneralCP1CI_AS.

    Among other things, this affects to TempDB collation and all the rest of system databases. Now let's imagine we want to create/import an user database with a different collation, I want that the instance collation (hence Tempdb) to be aligned with the user database collation.

    Not having this option could bring performance issues in the future (tempdb is used by SQL Server Query Engine and queries execution plans), so it means automatically discarding…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Cloud SQL

Categories

Feedback and Knowledge Base