Cloud SQL True Cost & Upgrade Calculator

Compute is usually the largest line, but rarely the only one. Provisioned storage bills every hour whether the instance runs or not, backups bill by the GiB actually kept, high availability prices compute and storage at higher HA rates, each read replica is a separate instance with its own disk, SQL Server adds a license per core, and a version past community end of life adds extended support. Network transfer to the internet or another region is charged per GiB. The itemized table shows each of these as its own line.

An HA instance keeps a standby in a second zone, and Google prices it with separate HA rates for vCPU, memory, storage, data cache and extended support. In us-central1 the HA vCPU rate is exactly twice the zonal one, so HA roughly doubles compute and disk, while backups bill at one rate either way and SQL Server bills one license for the pair. The calculator shows the premium by component rather than as one multiplier. Whether it is worth it is a resilience question, not a pricing one.

Yes, as separate instance groups. Each group has its own machine type, region and availability, and is priced as a stand-alone instance with the primary's storage type and size. A replica in another region also adds replication traffic at the inter-region transfer rate, which you enter per group. The HA standby is part of the HA price and is never counted as a replica.

Dedicated-core CPU and memory in one region, for one or three years, at 25% or 52% off. They do not cover shared-core machine types, storage, backups, IP addresses, network transfer, SQL Server licenses or extended support. The fee is owed every hour of the term even if you stop, shrink or delete the instance, and usage above the commitment is billed at on-demand rates. Enter an existing commitment to see the fee, the usage it covers and any part left unused.

It depends on the version, and Google publishes the dates. MySQL 8.0 enters extended support on 1 January 2027 and PostgreSQL 14 on 1 February 2027. MySQL 5.6 and 5.7 and PostgreSQL 9.6 to 12 have been in it since 1 February 2025 and were charged from 1 May 2025. A version stays in extended support for up to three years at two rates, then Google upgrades it automatically. The support timeline on this page shows the dates and the monthly charge for your configuration.

No. A major version upgrade and a move to Enterprise Plus are separate decisions, and the calculator keeps your current edition and machine after the upgrade unless you change them. It also does not assume an upgrade makes the database faster or lets you use a smaller machine. MySQL upgrades in place one major version at a time; for PostgreSQL, check the versions your instance lists as upgradable.

Stopping an instance stops the compute charge, and with it SQL Server licensing and extended support, which bill only while the instance runs. Provisioned storage, backups and a public IPv4 address keep billing, the address at the idle rate. A commitment's fee is owed regardless. Read replicas cannot be stopped, so the calculator keeps them running every hour.

Because the billable size cannot be worked out from the database size. Backups are incremental, compress differently and depend on how much data changes between them, so database size times the number of copies kept is usually wrong in either direction. Enter the backup GiB from your bill or the instance's backups page. Until you do, the estimate leaves backups out and says so.

Taxes, negotiated pricing and credits; serverless export fees; Cloud DNS; connectivity such as Interconnect ports or VPN; transfer charged by the sending side; and anything you leave as not entered. Rates are USD list prices from Google's pricing page. Whenever an input is unknown or a rate is not published for your configuration, the figure is labeled a modeled subtotal and the missing parts are listed.

Both scenarios are priced day by day over the dates you choose: keep the current version, or upgrade on your completion date. Each day uses the support rate in force that day, so rate changes, waivers and deprecation are respected. Project costs you enter (engineering, testing, downtime, a temporary duplicate environment) are added to the upgrade scenario. The net benefit is the difference, and break-even is the first day the cumulative benefit is no longer negative. Nothing is extrapolated past the forecast end.