Running a Manual Merge

The RLV store is self-managing and performs automatic merges, as needed. However, in a few cases, you may wish to trigger a merge manually.

Prerequisites

Task

Some reasons you might consider a manual merge include

When you are preparing to perform a table-level load (to ensure that the DDL or load command performance is not impacted by an automatic merge). You would run a blocking merge in this instance.
To free memory before a DML operation, such as a bulk load, on a table which is known to affect a large data volume (to ensure that an automatic merge does not run concurrently with the DML command). You would run a blocking merge in this instance.
Prior to shutdown, in order to reduce startup time (otherwise, RLV recovery will be performed, which may be time-consuming).
If the automated merge period is set to a large time, and system resources are approaching threshold limits. You would run a non-blocking merge in this instance, but would also modify the times and thresholds so that you would not need to monitor as closely in the future.

To manually run an RLV merge, use the SQL stored procedure sp_iqmergerlvstore [ [ merge_type ], [ table_name ], [ table_owner ] ].

If a table name is not specified, all the active data (from all RLV-enabled tables) in the RLV store will be merged into the IQ main store.
Merge-type can be BLOCKING | NON-BLOCKING .
After performing the merge, the stored procedure will automatically commit the merge transaction.