Progress
Client Deployment
Guide


Reducing Connection Times

To perform database activities, the Progress client keeps a copy of the database schema, called the schema cache, in memory. By default, Progress creates the schema cache by reading the database schema stored in the database file. The client reads the schema in two parts:

The time required to read the schema is usually minimal. However, the time required to read the schema might be unacceptable under the following conditions:

To reduce the amount of time required to connect, Progress lets you store the schema cache as a binary file, called a schema cache file, on a local disk. The client can then read the schema directly from the schema cache file.

To create the schema cache file, you build the desired schema cache and save it to a binary file using the Progress statement SAVE CACHE. The schema cache file is portable across systems, so you can create the file once and distribute it across a heterogeneous network of systems. For information about building and saving the schema cache file, see the Progress Programming Handbook. For information about the SAVE CACHE statement, see the Progress Language Reference.

To connect using the local schema cache file, specify the Schema Cache File (-cache) startup parameter when you connect to a database. If the schema cache file is valid, Progress reads the schema from the local file instead of from the database. The schema cache is valid if the time stamp of the schema cache file matches the time stamp in the database master block. If the time stamps do not match, or for some reason Progress cannot read the file, Progress issues a warning message and reads the schema from the database. For information about the Schema Cache File (-cache) startup parameter, see the Progress Startup Command and Parameter Reference.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095