Table of Contents
- 2.1 Before You Begin
- 2.2 Loading Data
- 2.3 Running Queries
- 2.4 Modifying Tables
- 2.5 Unloading Data
- 2.6 Table Load and Query Example
- 2.7 Workload Optimization
- 2.8 Workload Optimization using Advisor
- 2.9 Best Practices
- 2.10 Supported Data Types
- 2.11 Supported SQL Modes
- 2.12 Supported Functions and Operators
- 2.12.1 Aggregate Functions
- 2.12.2 Arithmetic Operators
- 2.12.3 Cast Functions and Operators
- 2.12.4 Comparison Functions and Operators
- 2.12.5 Control Flow Functions and Operators
- 2.12.6 Data Masking and De-Identification Functions
- 2.12.7 Date and Time Functions
- 2.12.8 Encryption and Compression Functions
- 2.12.9 Logical Operators
- 2.12.10 Mathematical Functions
- 2.12.11 String Functions and Operators
- 2.12.12 Window Functions
- 2.13 String Column Encoding Reference
- 2.14 Troubleshooting
- 2.15 Metadata Queries
- 2.16 Limitations
When a HeatWave Cluster is enabled, queries that meet certain prerequisites are automatically offloaded from the MySQL DB System to the HeatWave Cluster for accelerated processing.
Queries are issued from a MySQL client or application that interacts with the HeatWave Cluster by connecting to the MySQL DB System. Results are returned to the MySQL DB System and to the MySQL client or application that issued the query.
Manually loading data into HeatWave involves preparing tables on the MySQL DB System and executing load statements. See Section 2.2.2, “Loading Data Manually”. The Auto Parallel Load utility facilitates the process of loading data by automating required steps and optimizing the number of parallel load threads. See Section 2.2.3, “Loading Data Using Auto Parallel Load”.
For MySQL HeatWave on AWS, you can load data into HeatWave using the MySQL HeatWave Console. See Manage HeatWave Data with Workspaces, in the MySQL HeatWave on AWS Service Guide.
For HeatWave in Oracle Database Service for Azure (ODSA), see Importing Data to MySQL HeatWave.
When HeatWave loads a table, the data is sharded and distributed among HeatWave nodes. After a table is loaded, DML operations on the tables are automatically propagated to the HeatWave nodes. No user action is required to synchronize data. For more information, see Section 2.2.7, “Change Propagation”.
On Oracle Cloud Infrastructure (OCI), data loaded into HeatWave, including propagated changes, are automatically persisted by the HeatWave Storage Layer to OCI Object Storage for a fast recovery in case of a HeatWave node or cluster failure. For MySQL HeatWave on AWS, data is recovered from the MySQL DB System.
After running a number of queries, you can use the HeatWave Advisor to optimize your workload. Advisor analyzes your data and query history to provide string column encoding and data placement recommendations. See Section 2.8, “Workload Optimization using Advisor”.