Product Documentation

Database Administrator's Guide

Previous Topic

Next Topic


NO_CACHE <data file name>

In some cases, it might be beneficial to define that a certain file NOT be cached. For example, if a file contains very large variable length records (BLOBS), it might be more efficient to bypass the cache and rely solely on the operating systems cache support. The FairCom Server does not store the full variable length record in cache, but retains the first and last page of the variable length record. This prevents large blocks of data from consuming the cache and also alleviates the management of a large number of cache pages for any one particular record. NO_CACHE disables cache for a given file.

Note: <data file name> may include a wildcard pattern using ‘?’ for a single character and ‘*’ for zero or more characters. See FairCom DB Standard Wildcards. The Server Administrator can specify multiple NO_CACHE configuration entries.

Caching can only be turned off for entire superfiles (i.e., the superfile host), not for individual superfile members. Index files require the use of index cache pages and must be cached.

Default: Cache files