[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["# Diagnose issues\n\n\u003cbr /\u003e\n\n[MySQL](/sql/docs/mysql/diagnose-issues \"View this page for the MySQL database engine\") \\| [PostgreSQL](/sql/docs/postgres/diagnose-issues \"View this page for the PostgreSQL database engine\") \\| SQL Server\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThis page contains a list of the most frequent issues you might run into\nwhen working with Cloud SQL instances and steps you can take to address\nthem. Also review the\n[Known issues](/sql/docs/sqlserver/known-issues),\n[Troubleshooting](/sql/docs/sqlserver/troubleshooting), and\n[Support page](/sql/docs/sqlserver/support) pages.\n\nView logs\n---------\n\nTo see information about recent operations, you can view the\n[Cloud SQL instance operation logs](/sql/docs/sqlserver/logging#logs)\nor the [SQL Server error logs](/sql/docs/sqlserver/logging).\n\nConnection issues\n-----------------\n\nSee the [Debugging connection\nissues](/sql/docs/sqlserver/debugging-connectivity) page or the [Connectivity](/sql/docs/sqlserver/troubleshooting#connectivity) section in the troubleshooting page for help with connection\nproblems.\n\nInstance issues\n---------------\n\n### Backups\n\nFor the best performance for\n[backups](/sql/docs/sqlserver/backup-recovery/backups), keep the\nnumber of tables to a reasonable number.\n\nFor other backups issues, see the [Backups](/sql/docs/sqlserver/troubleshooting#backups) section in the troubleshooting page.\n\n### Import and export\n\nImports into Cloud SQL and exports out of Cloud SQL can take a long time to complete,\ndepending on the size of the data being processed. This can have the following impacts:\n\n- You can't stop a long-running Cloud SQL instance operation.\n- You can perform only one import or export operation at a time for each instance, and a long-running import or export blocks other operations, such as daily automated backups.\n\nYou can decrease the amount of time it takes to complete each operation by using the\nCloud SQL import or export functionality with smaller batches of data.\n\n\nFor whole database migrations, you generally should use BAK files rather than SQL files for\nimports. Generally, importing from a SQL file takes much longer than importing from a BAK file.\n\nFor other import and export issues, see the [Import and export](/sql/docs/sqlserver/troubleshooting#import-export) section in the troubleshooting page.\n\n\u003cbr /\u003e\n\n### Suspended state\n\nThere are various reasons why Cloud SQL may suspend an instance,\nincluding:\n\n- Billing issues\n\n For example, if the credit card for the project's billing account has\n expired, the instance may be suspended. You can check the billing\n information for a project by going to the Google Cloud console\n [billing page](https://console.cloud.google.com/billing), selecting the project, and viewing\n the billing account information used for the project. After you resolve\n the billing issue, the instance returns to runnable status within\n a few hours.\n- Key issues with Cloud Key Management Service\n\n For example, if the key version of the Cloud KMS that's used to encrypt the user data in the Cloud SQL instance isn't present, access to the key is revoked, or if the key is deactivated or deleted. For more information, see [Using customer-managed encryption keys (CMEK)](/sql/docs/sqlserver/configure-cmek).\n- Legal issues\n\n For example, a violation of the\n [Google Cloud Acceptable Use Policy](/terms/aup) may cause the\n instance to be suspended. For more information, see \"Suspensions and\n Removals\" in the [Google Cloud Terms of Service](/terms).\n- Operational issues\n\n For example, if an instance is stuck in a crash loop (it crashes\n while starting or just after starting), Cloud SQL may suspend it.\n\nWhile an instance is suspended, you can continue to view information about it\nor you can delete it, if billing issues triggered the suspension.\n\nCloud SQL users with Platinum, Gold, or Silver\n[support packages](/support) can contact our support team directly about\nsuspended instances. All users can use the earlier guidance along with the\n[google-cloud-sql](http://stackoverflow.com/questions/tagged/google-cloud-sql)\nforum.\n\nPerformance\n-----------\n\n### Overview\n\nCloud SQL supports performance-intensive workloads with up to 60,000 IOPS\nand no extra cost for I/O. IOPS and throughput performance depends on disk size,\ninstance vCPU count, and I/O block size, among other factors.\n\nYour instance's performance also depends on your\n[choice of storage type](/sql/docs/sqlserver/choosing-ssd-hdd) and\nworkload.\n\nLearn more about:\n\n- [Persistent disks and performance](/compute/docs/disks/performance#size_price_performance).\n- [Performance and throttling metrics](/compute/docs/disks/performance#review_performance_and_throttling_metrics).\n- [Optimizing disk performance](/compute/docs/disks/performance#optimize_disk_performance).\n- [Other factors that affect performance](https://cloud.google.com/compute/docs/disks/optimizing-pd-performance#performance_factors).\n\n\u003cbr /\u003e\n\n### Keep a reasonable number of database tables\n\nDatabase tables consume system resources. A large number\ncan affect instance performance and availability, and cause the instance to\nlose its SLA coverage.\n[Learn more](/sql/docs/sqlserver/operational-guidelines).\n\n\u003cbr /\u003e\n\nTroubleshoot\n------------\n\nFor other Cloud SQL issues, see the [troubleshooting](/sql/docs/sqlserver/troubleshooting) page.\n\nError messages\n--------------\n\nFor specific API error messages, see the [Error messages](/sql/docs/error-messages) reference page.\n\nTroubleshoot customer-managed encryption keys (CMEK)\n----------------------------------------------------\n\n\nCloud SQL administrator operations, such as create, clone, or update, might fail due to\nCloud KMS errors, and missing roles or permissions. Common reasons for failure include a\nmissing Cloud KMS key version, a disabled or destroyed Cloud KMS key version,\ninsufficient IAM permissions to access the Cloud KMS key version, or the\nCloud KMS key version is in a different region than the Cloud SQL instance. Use the\nfollowing troubleshooting table to diagnose and resolve common problems.\n\n#### Customer-managed encryption keys troubleshooting table\n\n| **Note:** If the instance is in a failed state during the `create` operation, you must delete it, add the role to the account you are using, and create a new instance with an active Cloud KMS key version.\n\n#### Re-encryption troubleshooting table"]]
