Use a SELECT statement. INSERT ... SELECT and CREATE TABLE ... SELECT statements are supported,, but only the SELECT portion is offloaded to MySQL HeatWave.

See Section 5.4.4, “CREATE TABLE ... SELECT Statements”, and Section 5.4.6, “INSERT ... SELECT Statements”.

Define all tables accessed by the query using RAPID as the secondary engine.

Load all accessed tables in MySQL HeatWave.

Enable autocommit. If autocommit is disabled, MySQL HeatWave does not offload the query and execution is performed on the DB System. To check the autocommit setting:

mysql> SHOW VARIABLES LIKE 'autocommit';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| autocommit    | ON    |
+---------------+-------+

To execute queries using the MySQL HeatWave secondary engine, set the use_secondary_engine system variable ,to either ON or FORCED state using one of the following syntax options. By default, this variable is set to ON.

mysql> SET SESSION use_secondary_engine = 'ON';
Query OK, 0 rows affected (0.2831 sec)

mysql> SET SESSION use_secondary_engine = 'FORCED';
Query OK, 0 rows affected (0.3451 sec)

Ensure that queries use only functions and operators supported by MySQL HeatWave. See Section 5.3, “Supported Functions and Operators”.

Ensure that queries use only SQL modes supported by MySQL HeatWave.

Queries should not include any known limitations.