Select the MySQL edition in PD DigitalOcean MySQL before setting plans and high availability. The choice affects what you can offer for new database services.

Choose Engine on the offering

Open the package on Module Options, choose MySQL — Standard Edition or MySQL — Advanced Edition, save, then inspect the available plans, versions and High availability. Generate customer choices only after those defaults match the edition.

Apply the dated Standard Edition restrictions

New Standard Edition clusters are limited to 4 GiB RAM, without standby or read-only nodes, from 15 October 2026 for accounts that have never created either PostgreSQL or MySQL. The same restriction applies to new clusters for all accounts from 30 November 2026. Clusters created before the limit applies to the account are not affected by that provider change.

During the earlier account-history phase, the module cannot infer complete historical eligibility from the current cluster list. DigitalOcean can refuse an apparently available choice. From the all-account date, the module filters over-limit new-cluster choices itself. Review old generated options and prices before rebuilding them.

See DigitalOcean’s dated plan changes for the provider policy. Do not assume a visible plan overrides it.

Match the high-availability layout

The module requests three nodes for Advanced Edition MySQL with High availability enabled: a primary and two standby nodes. Eligible Standard Edition uses two nodes when its standby layout is allowed. Extra nodes affect provider costs, and availability still depends on the selected plan, region and account.

The client backup list is a separate capability: this module exposes it for Standard Edition, not Advanced Edition. Absence of that tab is not proof that the provider has no recovery facilities.

Keep conversion separate from resizing

An existing database retains its edition. Moving its service to an offering of the other edition is refused rather than treated as a conversion. If a different edition is required, arrange a new service and a separately managed data move. Do not repeatedly retry the same refused resize or assume the move has happened because the billing offering changed.

See the PD DigitalOcean MySQL Blesta guide for related setup, or explore PD DigitalOcean MySQL.