[[["이해하기 쉬움","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(UTC)"],[],[],null,["Before using your deployed SQL Server system, we recommend that you perform the\npost-deployment tasks described in this document.\n\nReview the deployment\n\nAfter successfully deploying a SQL Server workload, you can review the\ndeployment output and configuration on the dashboard.\n\nReview the deployment resources\n\nTo review the resources created during the deployment:\n\n1. Go to the Workload Manager page in the Google Cloud console.\n\n [Go to Workload Manager](https://console.cloud.google.com/workloads)\n2. In the left navigation pane, click **Deployments** to open the\n deployment dashboard.\n\n3. Select the name of the deployment to open the **Deployment information** page.\n\n4. Click **Deployment Output** tab to view a list of all resources that\n were created during the deployment, the resource type, and a link to the resource (if applicable).\n\nReview the deployment configuration\n\nTo review the deployment configuration:\n\n1. Go to the Workload Manager page in the Google Cloud console.\n\n [Go to Workload Manager](https://console.cloud.google.com/workloads)\n2. In the left navigation pane, click **Deployments** to open the\n deployment dashboard.\n\n3. Select the name of the deployment to open the **Deployment information** page.\n\n4. Click the **Details** tab to view the information that you've entered for\n the initial configuration of the deployment.\n\nModify the system post deployment\n\nIn [Preview](https://cloud.google.com/products?#product-launch-stages), Workload Manager does not\nsupport the ability to modify a deployment that was deployed within the console.\n\nOne option is to deploy a new system with the required settings and configurations,\nand then transfer any configuration or data from the original deployment.\nLater you can delete the original deployment once the transfer is\ncomplete and the new system is validated.\n\nAlternatively, you can manually modify a resource that was deployed using\nnormal modification methods outside of Workload Manager. However,\nthis causes the deployment object within Workload Manager and the\nunderlying Terraform state file to become out of sync with the actual state of the resources.\n\nDelete a deployment\n\nWhen deleting a deployment, the tool attempts to only delete the resources that\nwere created as part of the deployment. Shared resources or resources\nthat existed before the deployment, such as secrets and VPCs are not deleted.\n\nDeleting a resource is a permanent action and the resource or data residing on\nit is not recoverable. If you have not done so already, consider taking a backup of the system.\n\nTo delete a deployment, do the following:\n\n1. Go to the Workload Manager page in the Google Cloud console.\n\n [Go to Workload Manager](https://console.cloud.google.com/workloads)\n2. In the left navigation pane, click **Deployments** to open the\n deployment dashboard.\n\n3. Select the name of the deployment to open the **Deployment information** page.\n In the **Deployment Output** tab, review all the resources that were deployed\n as part of the deployment.\n\n4. Click **Delete** at the top of the deployment information page and then confirm the deletion.\n\nAdditional items that were used to deploy the system might remain after the system is deleted.\nYou can delete these items manually if you want to.\n\n- Within a Cloud Storage bucket:\n - The Cloud Build history and logs\n - The Terraform and state file used by the original deployment\n - The SQL Server Installation media used in the deployment\n- Service accounts\n - The Google-managed service account used by Workload Manager\n - The service account used by Cloud Build"]]
