Create a managed SQL Server offering after saving its Google Cloud connection. Saving the offering describes a future service; the intended activation process is what requests a real, chargeable instance.

Configure the offering

1. Open System Settings → Products/Services and create the intended product in its product group.
2. Choose Other Products/Services as the type. Under Module Settings, select PD Google Cloud SQL Server and the server group containing the intended Google Cloud connection.
3. Set Region, Plan, Engine version and Storage (GB). The module provisions SQL Server; the engine is fixed for this module.
4. Review Resource name prefix and the client feature controls below.
5. Review Automatically setup the product and choose the activation trigger intended for your order process. A saved product does not establish that this trigger is correct.
6. Save the product. Review checkout options separately on the module’s Products page before offering customer-selectable dimensions.

Generated checkout choices can override Module Settings defaults. Inspect the effective selected values, including hidden choices, when reviewing the offering.

Choose the database specification

Select the intended region, machine plan, engine version and starting storage. The module uses a maintained catalogue of choices; a listed choice is not confirmation of capacity, quota or every plan/version combination in your project. Confirm the intended configuration before opening the offering for orders.

Storage (GB) starts at a minimum of 10 GB in the module’s configuration. The module’s storage changes support increases, not reductions. Provisioning enables automatic storage growth, but this is not an unlimited-capacity or uninterrupted-service promise. Monitor capacity and growth costs; provider limits and workload spikes can still matter. Google explains the relevant instance storage settings.

The module uses the Cloud SQL Enterprise infrastructure edition. This is separate from the SQL Server engine edition selected in Engine version; it does not mean you selected SQL Server Enterprise. The provisioned instance is single-zone and has a public IP initially created with an empty authorised-network list. It does not offer regional high availability as a generated checkout dimension. Plan the application’s authorised source before expecting a direct public-IP connection.

Review the SQL Server edition

Engine version includes both the SQL Server year and its engine edition. The supplied choices include Express, Web and Standard for 2019 and 2022, and Express and Standard for 2025. The module does not offer SQL Server Enterprise as an engine choice, and there is no SQL Server 2025 Web choice. Google lists the provider’s SQL Server database versions.

Leaving the engine version blank uses the module’s fixed SQL Server 2022 Standard default. It is not a request for the newest provider version. Choose deliberately for the application and confirm that its features fit the selected SQL Server edition.

The module’s SQL Server plans are dedicated-core custom machine sizes. Do not copy a shared-core plan from another database offering or assume the maintained list contains every current provider machine type.

Decide what clients can manage

Review Client: Firewall, Client: Connection details, Client: Users and Client: Databases. These govern the corresponding service controls. Enable the actions your offering supports. The database user’s password is separate from the Google service-account credential; customers should never receive the provider key.

Review any Client Area Section text before showing it to customers. Keep provider credentials and private operational details out of that text.

Verify the intended activation

Preview the order form, effective resource choices and your own pricing. When ready, use your normal authorised provisioning test, recognising that it creates chargeable Google Cloud resources. Inspect Clients & Databases, Activity, the service state and the actual provider result. Keep the normal cron running for asynchronous progress.

A saved offering, a Ready options label or a passed connection test is not proof that the instance exists or accepts application connections. If the outcome is uncertain, reconcile it before repeating activation.

Do not send provider keys, database passwords or a full customer record.

See the PD Google Cloud SQL Server WHMCS guide for related setup, or explore PD Google Cloud SQL Server.