Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Google Cloud SQL vs DBmaestro, the Slant community recommends DBmaestro for most people. In the question“What are the best SQL Database as a Service providers?” DBmaestro is ranked 8th while Google Cloud SQL is ranked 10th. The most important reason people chose DBmaestro is:
JIRA, Azure DevOps, ServiceNow.
Question Ranking
Pros
Pro Supports automatic encryption
Google Cloud SQL automatically encrypts all tables and temporary files.
Pro Task management
JIRA, Azure DevOps, ServiceNow.
Pro CI tools
Jenkins, CloudBees, Bamboo, Octopus Deploy.
Pro Source control
Supports Git, Bitbucket, subversion, Azure, Perforce.
Pro Multi database
Oracle, Microsoft SQL Server, IBM DB2, PostgreSQL, EnterpriseDB, MySQL, MariaDB, RDS and Aurora.
Cons
Con AWFUL data integrity practice: Backup lifecycle is tied to instance lifecycle
If you are using Google CloudSQL, you are one command away from losing everything:
gcloud sql instances delete prod-instance-nameWhen you delete a CloudSQL instance, it also deletes the back-ups associated with that instance along with it. So if you accidentally delete your production database: Your backups? Poof. Gone.
It says this in the fine print of the on-demand backups documentation: https://cloud.google.com/sql/docs/mysql/backup-recovery/backups#about_on-dem
They persist until you delete them or until their instance is deleted.There is also no way to mark a CloudSQL instance as "protected" so one bad CLI command can lose you your production database and all backups.
In order to get an actual backup workflow that will not affect production traffic, you must:
Don't fall for it. Protect your production data. Avoid busywork caused by poor product design. Avoid Google CloudSQL.
Con Performance limits
There are some performance limits when dealing with transactions for Google Cloud SQL.
