Oracle Database@Google Cloud Pricing
Exadata Database Service
Oracle Database@Google Cloud is purchased through Google Cloud Marketplace. Pricing is the same as for Oracle Exadata Database Service running on OCI.
Exadata Database Service vCPUs
|
Product
|
Comparison Price
( /vCPU)* |
Unit Price
|
Unit
|
|
Exadata Database OCPU – Dedicated Infrastructure
|
OCPU per hour
|
||
|
Exadata Database OCPU – Dedicated Infrastructure – BYOL
|
OCPU per hour
|
Exadata Cloud Infrastructure X9M
|
Product
|
Unit Price
|
Unit
|
|
Exadata Cloud Infrastructure - Quarter Rack - X9M
|
|
Hosted Environment per hour
|
|
Exadata Cloud Infrastructure - Database Server - X9M
|
|
Hosted Environment per hour
|
|
Exadata Cloud Infrastructure - Storage Server - X9M
|
|
Hosted Environment per hour
|
Please visit the Oracle Cloud Price List for pricing information on other Exadata Database Service configurations.
- * To make it easier to compare pricing across cloud service providers, Oracle web pages show both vCPU (virtual CPUs) prices and OCPU (Oracle CPU) prices for products with compute-based pricing. The products themselves, provisioning in the portal, billing, etc. continue to use OCPU (Oracle CPU) units. OCPUs represent physical CPU cores. Most CPU architectures, including x86, execute two threads per physical core, so 1 OCPU is the equivalent of 2 vCPUs for x86-based compute. The per-hour OCPU rate customers are billed at is therefore twice the vCPU price since they receive two vCPUs of compute power for each OCPU, unless it's a sub-core instance such as preemptible instances.
- OCPUs are billed for active hours, per-second billing applies.
- For more information on Oracle Exadata Database Service, review the documentation.
Autonomous Data Warehouse
Autonomous Data Warehouse
Despliegue |
Producto |
Precio unitario |
Unidad |
|
| Modelo informático | ||||
|---|---|---|---|---|
- Sin servidor |
Oracle Autonomous Data Warehouse–ECPU |
ECPU por hora |
||
- Sin servidor |
Oracle Autonomous Data Warehouse–ECPU–BYOL |
ECPU por hora |
||
| Infraestructura | ||||
- Sin servidor |
Oracle Autonomous Data Warehouse Exadata Storage for ECPU |
Capacidad de almacenamiento en gigabytes por mes |
||
- Sin servidor |
Oracle Autonomous Database Backup Storage |
Capacidad de almacenamiento en gigabytes por mes |
||
Autonomous Data Warehouse se factura por ECPU. Consulta Preguntas frecuentes sobre Oracle Autonomous Database ECPU (PDF) para obtener información sobre las ECPU y la antigua métrica de OCPU.
Autonomous Transaction Processing
Autonomous Transaction Processing
Despliegue |
Producto |
Precio unitario |
Unidad |
| Modelo informático | |||
|---|---|---|---|
Sin servidor |
Oracle Autonomous Transaction Processing: ECPU |
ECPU por hora |
|
Sin servidor |
Oracle Autonomous Transaction Processing –ECPU–BYOL |
ECPU por hora |
|
| Infraestructura | |||
Sin servidor |
Oracle Autonomous Transaction Processing Exadata Storage for ECPU |
Capacidad de almacenamiento en gigabytes por mes |
|
Sin servidor |
Oracle Autonomous Database Backup Storage |
Capacidad de almacenamiento en gigabytes por mes |
|
Autonomous Transaction Processing se factura por ECPU. Consulta Preguntas frecuentes sobre Oracle Autonomous Database ECPU (PDF) para obtener información sobre las ECPU y la antigua métrica de OCPU.