database_price
Managed database SKU prices per Region.
Primary key: vendor_id, region_id, database_id, allocation, ha, ha_strategy. See the version history of this table on dbdocs.io.
Columns
| Column | Type | Constraints | References | Description |
|---|---|---|---|---|
vendor_id | VARCHAR(255) | PK | vendor.vendor_id | Reference to the Vendor. |
region_id | VARCHAR(255) | PK | region.region_id | Reference to the Region. |
database_id | VARCHAR(255) | PK | database.database_id | Reference to the Database. |
allocation | ENUM | PK | Allocation method, e.g. on-demand or spot. See Allocation for the possible values. | |
ha | ENUM | PK | HA level this price applies to. See DatabaseHaLevel for the possible values. | |
ha_strategy | ENUM | PK | HA strategy this price applies to. See DatabaseHaStrategy for the possible values. | |
unit | ENUM | NOT NULL | Billing unit of the pricing model. See PriceUnit for the possible values. | |
price | FLOAT | NOT NULL | Actual price of a billing unit. | |
price_upfront | FLOAT | NOT NULL | Price to be paid when setting up the resource. | |
price_tiered | JSON | NOT NULL | List of pricing tiers with min/max thresholds and actual prices. | |
currency | VARCHAR(255) | NOT NULL | Currency of the prices. | |
status | ENUM | NOT NULL | Status of the resource (active or inactive). See Status for the possible values. | |
observed_at | DATETIME | NOT NULL | Timestamp of the last observation. |
Foreign keys
vendor_id,region_id→region(vendor_id,region_id)vendor_id,database_id→database(vendor_id,database_id)vendor_id→vendor(vendor_id)
Enums
Allocation
Server allocation options.
| Value | Description |
|---|---|
ONDEMAND | On-demand server. |
RESERVED | Reserved server. |
SPOT | Spot/preemptible server. |
DatabaseHaLevel
High availability level for a managed database type.
| Value | Description |
|---|---|
NONE | No high availability. |
SINGLE_ZONE | Single-zone high availability, meaning multiple databases in the same zone with failover or multi-master. |
MULTI_ZONE | Multi-zone high availability, meaning multiple databases in multiple zones of the same region with failover or multi-master. |
MULTI_REGION | Multi-region high availability, meaning multiple databases in multiple regions with failover or multi-master. |
DatabaseHaStrategy
High availability replication strategy for a managed database type.
| Value | Description |
|---|---|
NONE | No high availability strategy. |
PASSIVE_STANDBY | Passive standby for failover, e.g. standard RDS Multi-AZ with block storage replication. |
READABLE_CLUSTER | Readable cluster for read scaling and failover, e.g. RDS Multi-AZ Cluster / Aurora with engine replication. |
MULTI_MASTER | True multi-master, e.g. CockroachDB / Spanner / DynamoDB Global Tables. |
PriceUnit
Supported units for the price tables.
| Value | Description |
|---|---|
YEAR | Price per year. |
MONTH | Price per month. |
HOUR | Price per hour. |
GIB | Price per gibibyte (GiB). |
GB | Price per gigabyte (GB). |
GB_MONTH | Price per gigabyte (GB)/month. |
Status
Last known status of a resource, e.g. active or inactive.
| Value | Description |
|---|---|
ACTIVE | Active and available resource. |
INACTIVE | Unavailable. For Server/Database: temporary or unknown cause. |
PLANNED_FOR_RETIREMENT | Planned for retirement; only valid for Server and Database. |
RETIRED | Not orderable anymore, but prices may still exist (e.g. active multi-year contracts). Only valid for Server and Database. |