Database Cache
This form lets you control how much memory is used by
the CV11 client process to cache database information.
CV11 Server parameters are set in the 'rdmserver.ini' file in
the 'catalog' folder under the CV11 home directory.
For example, "C:\CV11\catalog\rdmserver.ini"
Technical Notes
The cache discussed above is a database cache on each
workstation. This cache is controlled by the Collect! database
engine, and in multi user operation is synchronized with the
server to ensure the cache data is valid despite editing activity
by other Users on the network.
The trick with using the database cache is that caching a
database in a multi user system is very different from caching
a word processor document using a regular disk cache.
A regular disk cache doesn't need to worry about whether
someone else could have changed anything while I was
looking at it. The database cache however had better be sure
that when I have a local image of a part of the database in RAM
the database files cannot be altered by someone else. It does
this by caching information only during the time records are
locked. Once records are unlocked the cache is considered
invalid since other Users could have made changes while the
records were unlocked.
Sync Files
Not used.
Remote Sync
Not used.
Truename
Not used.
Share As
Not used.
Inhibit Unc
Not used.
Enable Short Names
Not used.
Cache Pages
This is the maximum number of database pages (1024
bytes per page) that can be stored locally in RAM.
Increase cache to increase performance.
Whenever Collect! reads information from the database
the data is stored locally in RAM memory, so the next
time the data is accessed it can be read from local
RAM instead of the hard disk. Since RAM is so much
faster than a disk this can improve speed dramatically.
Increasing the size of the local cache can increase
performance (up to a point) on workstations. This is
especially noticeable when performing batch operations.
Overflow Pages
If the write operations during a transaction
write to more than the specified number of
database pages, then the User's LOG file
will be written to. Collect! allows you to
increase this value to increase performance on
workstations which perform many complex write
operations to the database (i.e. supervisor
or system manager workstations).
Help
Press this button for help on the
Database Cache form and links
to related topics.
Cancel
Selecting this button will ignore any changes you
have made and return you to the previous form.
OK
Selecting this button will save any changes
you have made and return you to the previous form.
|
Was this page helpful? Do you have any comments on this document? Can we make it better? If so how may we improve this page.
Please click this link to send us your comments: helpinfo@collect.org