HeatWave SQL is Oracle's in-memory query accelerator for MySQL Database Service, unifying OLTP and OLAP workloads in a single database. It eliminates complex ETL processes and follows a subscription-based, pay-as-you-go licensing model on Oracle Cloud Infrastructure. This guide covers the technology, licensing mechanics, deployment strategies, and cost optimisation approaches.
This guide is part of our Oracle licensing series. For the complete MySQL overview, see MySQL Licensing: A Complete Guide. For MySQL editions, see MySQL Editions Explained.
HeatWave SQL is an in-memory query accelerator built into Oracle's MySQL Database Service on Oracle Cloud Infrastructure (OCI). It simultaneously handles real-time analytics and transactional workloads within the same database, delivering high-speed performance and significant cost efficiency.
By integrating advanced in-memory analytics directly into MySQL, HeatWave eliminates the need for complex Extract, Transform, Load (ETL) processes. Organisations no longer need to maintain separate data warehouses or move data between systems to run analytical queries. Everything runs against the same live transactional database.
| Feature | Description | Business Impact |
|---|---|---|
| Unified Workloads | Supports OLTP and OLAP within a single database | Eliminates need for separate data warehouses and ETL infrastructure |
| In-Memory Processing | All analytical data processed entirely in memory | Reduces query latency from minutes to sub-seconds |
| Simplified Architecture | No separate databases or ETL processes required | Reduces infrastructure complexity and operational overhead |
| Node-Based Scalability | Easily scales with additional HeatWave nodes | Handles growing datasets and concurrent users without re-architecting |
| MySQL Native Integration | Fully integrated into MySQL Database Service | Minimal configuration changes to existing MySQL applications |
| Parallel Processing | Distributes workloads across multiple nodes simultaneously | Accelerates complex analytical queries by orders of magnitude |
| Advanced Compression | Sophisticated compression and indexing techniques | Reduces memory usage while maintaining high query performance |
HeatWave SQL is available as part of the MySQL Database Service on Oracle Cloud Infrastructure. It is not a standalone product. Organisations subscribe to the MySQL Database Service and select HeatWave as an additional option.
| Licensing Aspect | Details |
|---|---|
| Product Type | Add-on feature within MySQL Database Service (not standalone) |
| Pricing Model | Subscription-based, pay-as-you-go. Pay only for resources consumed. |
| Primary Cost Driver | Number and size of HeatWave nodes deployed |
| Price Variables | Geographic region, node size, associated MySQL database resources |
| Included Features | In-memory analytics, parallel processing, OCI integration, monitoring tools, technical support |
| ETL Tool Licensing | Not required. HeatWave eliminates the need for external ETL tools entirely. |
| Scaling Model | Add or remove nodes on demand. No commitment changes required. |
Understand the full cost picture. While HeatWave eliminates ETL tool licensing, the total cost depends on the number of HeatWave nodes, the MySQL Database Service tier, storage volumes, and data egress charges. Use Oracle's cost estimation tools before committing, and factor in expected data growth when projecting costs over a multi-year period.
| Factor | What to Assess | Impact on Cost | Priority |
|---|---|---|---|
| Dataset Size | Volume of data to be loaded into HeatWave memory | Directly determines number of nodes required | High |
| Query Complexity | Nature and complexity of analytical queries | Affects node compute requirements and sizing | Medium |
| Concurrent Users | Expected simultaneous query demand | May require additional nodes for sustained throughput | Medium |
| Geographic Region | OCI region where HeatWave is deployed | Node pricing varies significantly by region | Medium |
| Data Growth Rate | Annual increase in data volumes | Determines future node expansion and cost trajectory | High |
| Strategy | Description | Potential Savings |
|---|---|---|
| Right-size nodes | Start with minimum node count and scale based on actual performance. Avoid over-provisioning. | 20-40% |
| Leverage auto-scaling | Use OCI's auto-scaling capabilities to dynamically adjust nodes based on workload demand. | 15-25% |
| Optimise data loading | Only load the most frequently queried data into HeatWave memory. Not everything needs to be in-memory. | 10-30% |
| Negotiate committed use | If workloads are predictable, negotiate committed-use discounts with Oracle for sustained node reservations. | 20-40% |
| Monitor and prune | Regularly review node utilisation and eliminate underused nodes. Cloud sprawl affects HeatWave too. | 10-20% |
| Consider region pricing | Deploy in OCI regions with lower pricing where data residency requirements permit. | 5-15% |
Do not accept Oracle's list pricing without negotiation. Like all Oracle cloud services, HeatWave pricing is negotiable, particularly for larger deployments or longer-term commitments. Leverage competitive alternatives (Amazon Aurora, Google AlloyDB, Azure Database for MySQL) as bargaining chips during contract discussions.
HeatWave SQL is an in-memory query accelerator integrated into Oracle's MySQL Database Service on Oracle Cloud Infrastructure. It enables real-time analytics on live transactional data without requiring separate data warehouses or ETL processes.
No. HeatWave is exclusively an add-on to Oracle's MySQL Database Service on OCI. You cannot purchase or deploy it independently. You must first subscribe to the MySQL Database Service.
Pricing follows a pay-as-you-go subscription model based on the number and size of HeatWave nodes deployed. Costs vary by OCI region, node configuration, and associated MySQL database resources. Oracle provides cost estimation tools to project expenses before deployment.
No. This is one of HeatWave's primary advantages. By unifying OLTP and OLAP in a single database, it eliminates the need for external ETL processes and their associated licensing costs (e.g., Informatica, Talend, or Oracle Data Integrator).
Yes. The node-based architecture allows organisations to add or remove HeatWave nodes based on demand. The pay-as-you-go model means you only pay for what you actually consume, providing significant flexibility.
HeatWave is ideal for organisations that need real-time analytics on transactional data: e-commerce (real-time inventory analytics), finance (transaction analytics), logistics (supply chain optimisation), and any scenario where maintaining separate OLTP and OLAP systems creates operational overhead.
In most scenarios, yes. By eliminating separate data warehouses, ETL tools, and their associated infrastructure and licensing costs, HeatWave significantly reduces the total cost of ownership. However, conduct a proper TCO analysis for your specific workload before committing.