Progress
DataServer
for ORACLE Guide


Local Schema Caching

The ability to store schema definitions in a local file allows you to access them more quickly. Once you create a local schema cache, you have to connect to the schema holder only when you compile applications. You no longer rely on having a local schema holder for maximum performance. Running DataServer applications with a local schema cache instead of a schema holder also results in better performance.

The Progress 4GL SAVE CACHE COMPLETE statement creates a binary file that contains the entire schema for a Progress database. Use this syntax to create a cache file for a connected schema holder:

SAVE CACHE COMPLETE schema-holder-name TO filename. 

For example, the following statement creates a cache file named ocache for the oholder schema holder:

SAVE CACHE COMPLETE oholder TO ocache. 

To use the cache file for a schema holder, specify the -cache parameter and the cache filename when you connect to the schema holder. For example, the following CONNECT statement connects the ORACLE database with the schema holder and tells Progress to use the cache file:

CONNECT oholder -RO -db oradb -dt ORACLE -ld orademo -U scott -P tiger
-cache ocache. 

If you make any changes to the schema holder, create a new cache file for the schema holder.

For more information, see the Progress Programming Handbook and the SAVE CACHE Statement reference entry in the Progress Language Reference.


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