[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-11。"],[],[],null,["# Prerequisites for deploying a SQL Server workload\n\nThis document describes the prerequisites for deploying a SQL Server workload\non Google Cloud using Workload Manager.\n\nYou must first meet the [prerequisites for using the Guided Deployment Automation](/workload-manager/docs/deploy/prerequisites)\ntool before deploying a SQL Server workload.\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n### Configure networking resources\n\nThis section describes the Google Cloud networking resources that you need to\nconfigure before deploying the SQL Server workload.\n\n### VPC Network And Subnetwork\n\nAlthough your project has a default VPC and subnetwork (subnet), we recommend that\nyou create a new network so that the only firewall rules in effect are those\nthat you create explicitly.\n[Create a VPC network](/vpc/docs/create-modify-vpc-networks) and subnet\nor contact your Google Cloud organization's networking team.\n\n### Create a Cloud NAT gateway\n\nDuring the deployment process, VMs need outbound internet access to\ndownload packages and register for licensing. Google recommends that you create\na Cloud NAT gateway to provide external internet\naccess for your VMs without creating external IP addresses.\nYou can [create a Cloud NAT](/nat/docs/set-up-manage-network-address-translation#configure-nat)\nin each subnet and region in which your VMs are located.\n\nIf you don't want to use a Cloud NAT gateway, during the deployment process you\ncan specify external IP addresses to provide the required internet\naccess for your VMs.\n\nIAM permissions and roles\n-------------------------\n\nThe following permission is required to enable the Workload Manager API\nin the project where you're deploying the workload. This permission only needs to\nbe granted once in each project. An administrator or another user with this permission\ncan enable the API and other users will be able to access Workload Manager\nin the project.\n\nWorkload Manager also has roles to control who can access the deployment\noptions and determine who can deploy, manage, and view deployments. Each\nrole has the necessary permissions to perform the stated tasks. A complete list\nof the permissions assigned to each role can be found in the references section\nof the documentation.\n\nYou must also have the following permission to create the service accounts\nthat are used throughout the deployment process.\n\nSecrets for SQL Server workload\n-------------------------------\n\nThe Guided Deployment Automation tool uses Secret Manager to store passwords\nneeded during the deployment process. Plain text passwords are prohibited\nin accordance with our [Terraform best practices](/docs/terraform/best-practices-for-terraform#secrets).\n\nBefore using the Guided Deployment Automation tool,\nyou must [create at least one Secret](/secret-manager/docs/create-secret-quickstart)\nusing Secret Manager.\n\nMake sure to follow the [password complexity requirements](https://learn.microsoft.com/en-us/sql/relational-databases/security/password-policy?view=sql-server-ver16#password-complexity)\nfor SQL Server accounts.\nTo ensure that the secrets meet the password requirements from SQL Server,\nfollow the [SQL Server guidance for creating passwords](https://help..com/docs/SLTOOLSET/39c32e9783f6439e871410848f61544c/fe3f4554f82b1d5de10000000a44538d.html?version=CURRENT_VERSION_SWPM20&q=password).\n\nYou must create secrets in the project in which you deploy the SQL Server workload.\n\nQuotas\n------\n\nGoogle Cloud uses quotas to protect and control the number of resources that a\nparticular account or organization can use. SQL Server workloads often consume a\nlarge portion of resources. Given the size of the databases and applications,\nyou might experience quota issues during the deployment process.\n\nTo avoid quota issues, do the following:\n\n1. [View available resource quota for your project](/docs/quota#viewing_your_quota_console).\n2. If needed, [request a higher quota value](/docs/quotas/help/request_increase) or contact your project administrator.\n\nLicensing\n---------\n\nCustomers have a range of options for on-demand SQL Server and Windows Server\nlicenses directly from Google Cloud, and also the option to bring their own\nexisting licenses if those licenses meet the eligibility requirements.\nFor more information, see the [Microsoft licensing documentation](/compute/docs/instances/windows/ms-licensing).\n\nPrepare the SQL Server installation files\n-----------------------------------------\n\nFor SQL Server high availability (HA) configuration using bring your own license (BYOL),\nyou must create a Cloud Storage bucket\nin the project to hold the required installation media (ISO) file\nused during installation of SQL Server. Use the Google Cloud console to\n[create a Cloud Storage bucket](/storage/docs/discover-object-storage-console)\nfor storing the SQL Server installation files.\n\nAfter creating the bucket, upload the SQL Server installation\nISO file to the bucket by following your chosen method to\n[upload objects to a bucket](/storage/docs/uploading-objects#uploading-an-object).\n\nCreate an Active Directory domain\n---------------------------------\n\nBefore using the Guided Deployment Automation tool to deploy a SQL Server\nworkload, you need to set up the following:\n\n- An Active Directory domain with at least one domain controller.\n\n You can create an Active Directory domain by using [Managed Service for Microsoft Active Directory](/managed-microsoft-ad/docs/create-domain).\n Alternatively, you can [deploy a custom AD environment on {(compute_name)}](/architecture/deploy-an-active-directory-forest-on-compute-engine)\n and [set up a private DNS forwarding zone](/compute/docs/instances/windows/best-practices#use_cloud_dns_private_forwarding_zones)\n that forwards DNS queries to your domain controllers.\n- An Active Directory user who has permissions to join VMs to the domain and\n who can sign in by using RDP. If you're using Managed Microsoft AD, you\n can use the `setupadmin` user.\n\n- A Google Cloud project with a VPC network with connectivity to your AD\n domain controllers.\n\nWhat's next\n-----------\n\n- Learn how to [deploy a SQL Server workload](/workload-manager/docs/deploy/sql-server/deploy-sql)."]]
