Cloud SQL로 가져오고 Cloud SQL에서 내보내는 작업은 처리 중인 데이터의 크기에 따라 완료하는 데 많은 시간이 걸릴 수 있습니다. 이에 따른 영향은 다음과 같습니다.
장기 실행 Cloud SQL 인스턴스 작업을 중지할 수 없습니다.
각 인스턴스에 대해 한 번에 하나씩만 가져오기 또는 내보내기 작업을 수행할 수 있고 가져오기 또는 내보내기를 장기간 실행하면 일일 자동 백업과 같은 다른 작업이 차단됩니다.
더 작은 데이터 배치로 Cloud SQL 가져오기 또는 내보내기 기능을 사용하여 각 작업을 완료하는 데 걸리는 시간을 단축시킬 수 있습니다.
전체 데이터베이스 마이그레이션의 경우 SQL 파일 대신 BAK 파일을 가져오기에 사용합니다. 일반적으로 SQL 파일에서 가져오는 것이 BAK 파일에서 가져오는 것보다 훨씬 오래 걸립니다.
다른 가져오기 및 내보내기 문제는 문제 해결 페이지의 가져오기 및 내보내기 섹션을 참조하세요.
정지 상태
Cloud SQL에서 인스턴스를 정지할 수 있는 이유는 다음을 포함하여 다양합니다.
결제 문제
예를 들어 프로젝트 결제 계정의 신용카드가 만료되면 인스턴스가 정지될 수 있습니다. Google Cloud 콘솔의 결제 페이지에서 프로젝트를 선택하고 프로젝트에 사용된 결제 계정 정보를 조회하여 프로젝트의 결제 정보를 확인할 수 있습니다. 결제 문제를 해결하면 인스턴스가 몇 시간 내에 실행 가능한 상태로 돌아갑니다.
Cloud Key Management Service의 주요 문제
예를 들어, Cloud SQL 인스턴스에서 사용자 데이터를 암호화하는 데 사용되는 Cloud KMS의 키 버전이 없으면 키에 대한 액세스 권한이 취소되는 경우 또는 키가 비활성화되거나 삭제된 것입니다. 자세한 내용은 고객 관리 암호화 키(CMEK) 사용을 참조하세요.
Cloud KMS 오류, 역할 또는 권한 누락으로 인해 생성, 클론, 업데이트와 같은 Cloud SQL 관리자 작업이 실패할 수 있습니다. Cloud KMS 키 버전이 누락되거나, Cloud KMS 키 버전이 중지 또는 삭제되거나, Cloud KMS 키 버전에 액세스할 수 있는 IAM 권한이 없거나, Cloud KMS 키 버전이 Cloud SQL 인스턴스와 다른 리전에 있는 경우 등에는 일반적으로 작업이 실패하게 됩니다. 일반적인 문제를 진단하고 해결하려면 다음 문제해결 표를 사용하세요.
[[["이해하기 쉬움","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-08-19(UTC)"],[],[],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"]]
