Online Help > Data Sources




The caching mode will determine on how the client will re-load entries when changes are detected. On large data sources caching is a must and will increase performance significantly.



This feature requires an Advanced Data Sources.



If you feel the cache is outdated, press CTRL while clicking on refresh, this will force reading from the data source to recreate the cache.






Data source configuration - Caching mode

Data source configuration - Caching mode





No client caching.


Simple caching is the legacy caching mode. Performance may suffer when connected to data sources containing many sessions.


On a modification of data within a data source the server cache token is changed. When Password Vault Manager performs a refresh it will compare it's local cache token with the data source token. In the case where has changed the entire data source is reloaded.


Intelligent cache has the ability to handle many more sessions without experiencing performance degradation.


In the case of intelligent cache each modification performs a token update on the server. When Password Vault Manager performs a refresh action it will query the data source for any changes (delta) of changes to be applied client side since it last checked the data source. The delta of the changes is then sent to the application and applied locally.


When first opening the data source Password Vault Manager will loaded the session from the offline file then refresh to get the up-to date information.




The client cache is persisted to disk in %LocalAppData%\Devolutions\PasswordVaultManager\[GUID:DataSourceID]\Offline.db


There are two engines for the cache, if using a version of Password Vault Manager prior to 11.2, the default engine will be the SQLite, in that case the database is encrypted using a non-portable computed key hash.


If using version 11.2 or newer of Password Vault Manager the default cache engine will be the Microsoft Compound Document Format (MCDF) files.



You can enhance the security of the offline file by setting the Enhanced security in the options. See topic Offline Security



Depending on the configuration of the Caching Mode and the Offline Mode, the Offline.db file may still exist since the file servers as a dual purpose caching & offline line support.