Launch checklist for Cloud SQL
Introduction
ThisLaunch Checklist for Cloud SQL provides recommended activities tocomplete for launching a commercial application that uses Cloud SQL.This checklist focuses on Cloud SQL-specific activities. Touse the platform checklist,Launch Checklist for Google Cloud,to understand the activities also complete for all services.
ThisLaunch Checklist for Cloud SQL isdesigned for developers who are proficient with Cloud SQL. Ifyou are just starting out with Cloud SQL, these instructions will notteach you how to use Cloud SQL; instead, new users can start withaQuickstart guide.
This checklist is broken down into three sections:
- Architecture Design and Development
- Alpha Testing
- Final Launch
The sections are presented in the order we recommend that youuse them as you prepare to launch your application. For example, start with theArchitecture Design and Development Checklist; itcontains activities that we recommend you do early in your app's developmentlifecycle. Similarly, theAlpha Testing Checklist contains activities werecommend when you are closer to launch. However, the exact timeline of thechecklist activities and the time required for them depends on your applicationdevelopment time frame.
Architecture Design and Development Checklist
We recommend that you use this checklist in the early stages of the developmentof your application. You can work on the checklist activities in parallel;however, we recommend that you start the software architecture-relatedactivities as early as possible as they require more time to complete.
| Activity |
|---|
❑ Carefully assess the performance characteristics of Cloud SQL, a managed and replicated database service, and the service’s limitations andrestrictions (for example, no SUPER privilege). |
❑ Ensure that your DevOps team is familiar with theGoogle Cloud console, theSDK, and thegcloud CLI. All of these tools use the public Cloud SQL API. You can use either tool to create and manage instances, update user passwords, trigger restores, and complete other management tasks. You can also use third-party management tools, because Cloud SQL uses standard wire protocols. |
❑ ConsultCloud SQL community support on Stack Overflow for information and practical advice about Cloud SQL. |
❑ Subscribe to theCloud SQL announce group. Posts are made to this group for service updates and issue and incident reports. TheGoogle Cloud Status Dashboard also provides information about Cloud SQL and other Google Cloud services. |
Alpha Testing Checklist
Use theAlpha Testing Checklist when you are close to code complete and want toget initial metrics about your application.
| Activity |
|---|
❑ Remain current on the drivers that provide data access for your development platform. |
❑ Load-test early, often and realistically. Verify that your application can survive restarts of the Cloud SQL instance during maximum load. If your application is making a lot of connections, make sure the reconnect after a server restart has the right amount of backoff to avoid hitting the cap on the number of pending connections. For more information, see the FAQAre there any size or QPS limits? Be aware that a big, cold buffer will take quite some time to fill. Whenever possible, optimize queries to avoid the creation of temporary tables because operations involving temporary tables can be especially slow. |
❑ If you are connecting from Compute Engine, make sure the firewall behavior related to idle connections does not harm the application. If necessary, make sure to make the changes to TCP Keepalive persistent across reboots. For more information, seeConnecting to Cloud SQL from Compute Engine. |
❑ Observe theconnection limits for App Engine apps. Connection pools are the recommended way to achieve this. |
❑ Make sure there is a strategy in place for doing schema changes and the impact of doing them is well understood. We recommend that you create a clone of an instance to test a schema change. |
Final Launch Checklist
Use theFinal Launch Checklist shortly before and during your launch.
| Activity |
|---|
❑ There are no Cloud SQL specific activities for launch. If you have followed this checklist to this point, your project’s Cloud SQL service will be ready for your application’s launch. We recommend that you also review theFinal Launch Checklist in theLaunch Checklist for Google Cloud. |
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-11-24 UTC.