This documentation refers to PhraseExpress v16 beta. The documentation for current v15 is available here.

Database

Backup

PhraseExpress can create a backup file after every change to the local phrase file.

Select a backup storage location that differs from the storage location of your phrase file.

The backup location must have sufficient disk space. Example: If your phrase file size is 30MB you may need at least up to 300MB free disk space if you wish to keep a history of the last 10 versions.

PhraseExpress does not create backups for system phrase files (clipboard cache, etc.) and for SQL databases.

Backup your phrase file to multiple different (external) storage media. Hard disk can break and they do so when you rely on them the most!

SQL database caching

By default, phrase contents are requested from the SQL database in the moment of text insertion to ensure getting the most up-to-date content from the server. However, this request may cause a small delay, especially if PhraseExpress is connected to the SQL server over a internet connection.

To minimize network load and insertion delay, PhraseExpress can either preload all phrase contents of the entire database into the local computer memory at program startup.

Alternatively, PhraseExpress can keep the phrase contents in the local memomary after first insertion.after program launch. This means, the first insertion is slightly delayed but every subsequent insertion is instant.

Caching minimzes network load, removes the insertion delay but increases client memory consumption and startup time. Also, phrase contents are updated only once on program launch.

Caching of the entire database is limited to the currently select language.

Synchronization options

Checking and downloading updates of a shared phrase file creates network load and takes some time to process in the client. That is why the check for phrase file changes is manual.

Here you can configure PhraseExpress to automatically check for phrase file changes in the sync folder.

Considerations:
  • Checking on program launch takes the option that you to create and develop phrases before releasing your work to other users. Such work in progress is published to everyone on every program launch.
  • When you open the program window, PhraseExpress may be unresponsive until all changes have been processed.
  • Same happens if you close the PhraseExpress program window. It may take a while until you can continue to use PhraseExpress.

If up-to-date phrases are mission-critical, consider a SQL server where all users retrieve the most up-to-date phrases from the server at all times when using them.

Table of Contents


    Table of Contents