Microsoft® Repository changes are cached to improve performance. Guaranteed updates to a Repository are written to persistent storage only when the active transaction is committed.
Multiple Repository instances within the same process share a Repository cache. Within the same process, when a transaction for one Repository instance commits, its updates are immediately visible to transactions executing for other Repository instances. These updates are not visible to open Repository instances in other processes if those processes already have the pre-update data cached. Explicit refreshes are required to view updates from transactions that have completed in other processes.
To refresh a cache
This method invalidates unchanged cache data for the Repository item. Subsequent requests for that data will be fulfilled by retrieving the data from the Repository database.
-or-
Refresh all Microsoft Repository items currently cached for an open Repository instance by invoking the Refresh method associated with that Repository instance.
This method invalidates unchanged cache data for all Repository items. Subsequent requests for that data will be fulfilled by retrieving the data from the Repository database.
In addition to explicit refreshes, Microsoft Repository items may be refreshed implicitly at any time by the Repository engine, due to execution of internal Repository caching algorithms.