Oracle Database@Azure is purchased through the Microsoft Azure Marketplace, but pricing is the same as for Oracle Exadata Database Service running on OCI.
Product |
Comparison Price ( /vCPU)* |
Unit Price |
Unit |
Exadata Database OCPU – Dedicated Infrastructure |
OCPU per hour |
||
Exadata Database OCPU – Dedicated Infrastructure – BYOL |
OCPU per hour |
Service |
Unit price |
Unit |
Exadata Cloud Infrastructure - Database Server - X11M |
Hosted environment per hour |
|
Exadata Cloud Infrastructure - Storage Server - X11M |
Hosted environment per hour |
Please visit the Exadata pricing page for pricing information on Exadata Database Service configurations.
For more information on Oracle Exadata Database Service, review the documentation.
Product |
Unit Price |
Unit |
Oracle Exadata Exascale Database ECPU |
ECPU per hour |
|
Oracle Exadata Exascale Database ECPU - BYOL |
ECPU per hour |
Product |
Unit Price |
Unit |
Oracle Exadata Exascale RDMA Compute Infrastructure |
ECPU per hour |
|
Oracle Exadata Exascale Smart Database Storage |
Gigabyte (GB) storage capacity per month |
|
Oracle Exadata Exascale Additional Flash Cache |
Gigabyte (GB) per hour |
|
Oracle Exadata Exascale VM Filesystem Storage |
Gigabyte (GB) storage capacity per month |
Exadata Exascale ECPUs have a 48-hour minimum commitment and 8 ECPU minimum per virtual machine. If a database instance is terminated less than 48 hours after it’s activated, billing will be for the full 48-hour period, then by the second after that. Each ECPU you add to the system is billed by the second, with a minimum usage period of 1 minute. For Bring-Your-Own-License (BYOL) details, including eligible Oracle on-premises software licenses and conversion rates (i.e., ratio requirement of software license metric to cloud equivalent metric), refer to the Oracle PaaS and IaaS Universal Credits Service Descriptions document.
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. Additional details supporting the difference between OCPU vs. vCPU can be accessed here.
OCPUs are billed for active hours, per-second billing applies.
For more information on Oracle Exadata Database Service, review the documentation.
Deployment |
Product |
Unit price |
Unit |
|
| Compute model | ||||
|---|---|---|---|---|
- Serverless |
Oracle Autonomous AI Lakehouse–ECPU |
ECPU per hour |
||
- Serverless |
Oracle Autonomous AI Lakehouse–ECPU–BYOL |
ECPU per hour |
||
| Infrastructure | ||||
- Serverless |
Oracle Autonomous AI Lakehouse Exadata Storage for ECPU |
Gigabyte storage capacity per month |
||
- Serverless |
Oracle Autonomous AI Database Backup Storage |
Gigabyte storage capacity per month |
||
Autonomous AI Lakehouse is billed by ECPUs. See the Oracle Autonomous AI Database ECPU FAQ (PDF) for information on ECPUs and the older OCPU metric.
Deployment |
Product |
Unit price |
Unit |
| Compute model | |||
|---|---|---|---|
Serverless |
Oracle Autonomous AI Transaction Processing–ECPU |
ECPU per hour |
|
Serverless |
Oracle Autonomous AI Transaction Processing –ECPU–BYOL |
ECPU per hour |
|
| Infrastructure | |||
Serverless |
Oracle Autonomous AI Transaction Processing Exadata Storage for ECPU |
Gigabyte storage capacity per month |
|
Serverless |
Oracle Autonomous AI Database Backup Storage |
Gigabyte storage capacity per month |
|
Autonomous AI Transaction Processing is billed by ECPUs. See the Oracle Autonomous AI Database EPU FAQ (PDF) for information on ECPUs and the older OCPU metric.
Product |
Unit Price |
Unit |
Oracle Base Database Service – Standard - ECPU |
ECPU per hour |
|
Oracle Base Database Service – Enterprise - ECPU |
ECPU per hour |
|
Oracle Base Database Service – High Performance - ECPU |
ECPU per hour |
|
Oracle Base Database Service – BYOL - ECPU |
ECPU per hour |
|
Oracle Base Database Service – Database Storage |
Gigabyte storage capacity per month |
Base Database Service with ECPU pricing is available for standard x86 shapes running in Oracle Database@Azure.
For Bring-Your-Own-License (BYOL) details, including eligible Oracle on-premises software licenses and conversion rates (i.e., ratio requirement of software license metric to cloud equivalent metric), refer to the Oracle PaaS and IaaS Universal Credits Service Descriptions document (PDF).
Storage billing is measured with the Gigabyte Storage Capacity Per Month metric by calculating the total block volume storage consumed for each calendar month until the block volumes are deleted. At a minimum, users will be charged for 1 minute. For anything beyond 1 minute, usage is tracked per second and prorated based on the number of seconds in a month using the per Gigabyte Storage Capacity Per Month pricing.
Product |
Comparison price ( /vCPU)* |
Unit price |
Unit |
Oracle Cloud Infrastructure - GoldenGate |
OCPU per hour |
||
Oracle Cloud Infrastructure - GoldenGate - BYOL |
OCPU per hour |
*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.