Cloud SQL

  1. Cloud SQL for Singapore Data Center

    It will be better to have SQL and compute engine in the same data center for better perfomance and speed

    44 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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…

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add Support for MS SQL Server

    We use MS SQL Server and not MySQL, therefore we cannot use Google's Cloud SQL product. We would like to though.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks, the team is evaluating this and would like to provide it at some point in the future. It’s great to hear about your interest in a managed MSSQL offering, and I hope we’ll hear from many others who also want this. :)

  4. Mysql instances should also have a private network

    Managed mysql should have an internal ip address on the private network.

    131 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 87 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Managed PostgreSQL

    I would love you guys to have a managed PostgreSQL option for your Cloud SQL. It should offer the same features as MySQL where it automates replication, patch management and database management.

    292 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    25 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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 :)

    80 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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.cmd_func(cli=self, args=args)
    

    File "/usr/bin/../lib/google-cloud-sdk/./lib/googlecloudsdk/calliope/backend.py", line 1191,…

    82 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    29 comments  ·  Flag idea as inappropriate…  ·  Admin →
2 Next →
  • Don't see your idea?

Cloud SQL

Categories

Feedback and Knowledge Base