SET Residency

>>-SET--+-TABLE-+--name--+-------------------+------------------>
        '-INDEX-'        |    .-,-------.    |
                         |    V         |    |
                         '-(----dbspace-+--)-'
 
>--+-MEMORY_RESIDENT-+-----------------------------------------><
   '-NON_RESIDENT----'

Element	Description	Restrictions	Syntax
dbspace	The dbspace where fragment resides	The dbspace must exist	Identifier, p. Identifier
name	Table or index for which the residency state will be changed	Table or index must exist	Database Object Name, p. Database Object Name

This statement was formerly supported by Dynamic Server, but it is ignored in current releases. Beginning with Version 9.40, Dynamic Server determines the residency status of indexes and tables automatically.

The SET Residency statement allows you to specify the tables, indexes, and data fragments that you want to remain in the buffer as long as possible. When a free buffer is requested, pages that are declared with the MEMORY_RESIDENT keyword are considered last for page replacement.

The default state is nonresident. The residency state is persistent while the database server is up. That is, each time the database server is started, you must specify the database objects that you want to remain in shared memory.

After a table, index, or data fragment is set to MEMORY_RESIDENT, the residency state remains in effect until one of the following events occurs:

You use SET Residency to set the database object to NON_RESIDENT.
The database object is dropped.
The database server is taken offline.

Only user informix can set or change the residency state of a database object.

SET Residency

Syntax

Usage