Why set the database cache on a per database basis instead of server-wide

By: Borland Staff

Abstract: What is the recomended way of setting the cache pages?

Problem:
InterBase allows you to set the number of database cache pages at
the database level or at the server level.  Which is the recommended 
way of setting the cache pages?

Solution:
**********************************************
The information in this article applies to:
* InterBase v5.x
**********************************************

It is recommended that the number of database cache pages be
set on a per database level instead of a server level.   There are several
reasons why it is recommended to set the cache pages at the database
level:

1) Setting the cache pages for each database allows for more control.  If you use 
the server default every database on the server will use that value (except for 
databases that have an explicit value set).  When setting the value per database 
you can optimize the number of cache pages for that specific database.

2) When you set the number of cache pages for a specific database the value
will remain with the database regardless of where the database is backed up and
restored.  If a database relies on the server's default value the number may change
if the database is backed up and restored to a different server.

Note: use gfix -buffers to set the number of database cache buffers for a specific
database.

Server Response from: ETNASC03