This is an old revision of the document!
If a Hashed Data Cache is used in a query, it can be seen using Omnidex query plans. The following query plan shows a “Build cache” step that builds the Hashed Data Cache, and then a subsequent “Retrieve” step that retrieves from the Hashed Data Cache.
----------------------------------- SUMMARY ----------------------------------- Select INDIVIDUALS.NAME, GENDERS.DESCRIPTION from INDIVIDUALS join GENDERS on INDIVIDUALS.GENDER = GENDERS.GENDER; Version: 5.2.01 (Compiled Feb 2 2012 21:29:57) Warnings: SEQUENTIAL_SCAN ----------------------------------- DETAILS ----------------------------------- Build cache {1} as (SELECT DESCRIPTION, GENDER FROM GENDERS) on 2; Retrieve INDIVIDUALS sequentially; Retrieve {1} using PK_GENDER = INDIVIDUALS.GENDER; Return INDIVIDUALS.NAME, GENDERS.DESCRIPTION; -------------------------------------------------------------------------------
The Hashed Data Cache is limited to 32MB of memory per table by default. This can be adjusted using the HDC_THRESHOLD option of the SELECT statement, which sets the maximum cache size, measured in MB.
See also: