Incremental Refresh May Cause Larger Hyper Files Than Full Refresh

To reduce the .hyper file size, use one of the following options:

Option 1: Full Refresh

Perform a full refresh to rebuild the .hyper file from scratch, eliminating fragmentation.

Option 2: Rewrite the Hyper File in an Optimized Format

Use the Developer tools Hyper API to rewrite the file.

Note: Rewriting the file using the same file format version as the source may not reduce the file size. This triggers a logical copy rather than a physical rebuild. In that case, use one of the following options:

1. Rewrite hyper file as a different version to force a full physical rebuild. For detailed steps, refer to Rewrite your Hyper file in an optimized format.
2. Use a CTAS (Create Table As Select) query that re-inserts data into a new Hyper file rather than copying it directly.
   For example, the following query creates a new table in the new database and copies all columns and rows from the old table into it.
   • Example: CREATE TABLE "Extract"."MyNewTable" AS SELECT * FROM old_db."Extract"."MyOldTable"