If the database validations (local or remote) for your batch are repetitive (the same data is repeatedly retrieved from the database) you may find it advantageous to cache these results locally. In such cases, a local cache reduces (and may possibly eliminate) the need for transferring data to the local workstations, thereby saving time.

Do not cache workstation lookup results

Select this option if you do not want to cache database validation results on the local workstation. The local workstation requires access to all referenced database(s) when each database validation lookup is performed. If your database lookup results are highly variable, this may be the best option.

Each workstation caches lookup results

Select this option to enable workstation-based caching of database validation results. If your database lookup results are frequently the same, this may be the best option. If you select this option, the data is cached in memory on the workstation.

If you also have the Each KCN Service caches lookup results selected, the data is cached both on the workstation and the KCN Service computer. In this case, the KCN service is used to connect to the referenced database(s), and the lookup results are cached at the workstation and within the KCN service.

Number of results to cache per workstation

This setting controls how many lookup result sets you want to keep in the workstation cache. You can select from 1 to 5000 results (the default is 100). If the specified number of result sets is exceeded, the oldest result set in the cache is discarded and the newest result set is added. Therefore, the cache always contains the most recently used result sets.

Discard cached results after period of time

Select this option to clear the cache and start fresh from time to time. If the contents of the source database are relatively static, there may be no advantage to flushing the cache. However, if the database contents are highly dynamic, the workstation cache may drift out of synchronization with the database.

For example, suppose a customer database is updated nightly, and you want the cache to reflect the updated records at the beginning of the next day. In this case, you might set this option to discard the cache every 12 hours (720 minutes). By the time workers arrive the next day, results from the prior day are discarded from the cache.

You can specify a period of up to 1440 minutes (24 hours) in one minute increments. The default is 60 minutes.

Note The workstation cache is cleared if the Validation or Verification module is closed. Cache within the Validation module is independent of the cache within the Verification module.