Optimizing databases for better performance on the enterprise server

Follow

If databases have become "bloated" over the years, optimization may become necessary. This is especially the case for databases that have been upgraded from very old versions over many years.

1.1) XML export


The best way to completely clean up your databases is to export them to XML format and then re-import them:

  • Stop the server service
  • Copy your databases to a local, temporary directory.
  • Load the old databases from there individually DIRECTLY in the client of version 12
  • Export the database to XML format (Extras/Export Wizard)
  • Create a new, empty database in PSWE format (DB Manager/New Database).
  • Import the XML file into the database (Extras/Import Wizard)
  • Make sure that your databases have the same file name and master password!

IMPORTANT: The following data will be lost during this operation:

  • User-defined symbols are lost. You can update these via Properties in the General tab, using the Update Symbols button, but you can do so again.
  • All attachments are lost. Therefore, you should convert them manually first, as shown in the next step.


1.2) Alternative to XML export


If you do not want to perform the XML export (for example, because you use too many attachments, and do not want to convert them manually to document types), proceed as follows:

  • Stop the server service
  • Load the old databases individually DIRECTLY in the client of version 12
  • Click on Database/Save as and save the database in pswe format.
  • Delete all user-defined icons (Delete properties/symbols)
  • Delete the history (Properties/Extended/Delete Password History)
  • At least manually convert the very large attachments into the "Document" format.

2) Convert the attachments

Delete attachments from your database and convert them to the newer type "Document". To do this, go to EXTRAS/CLEAN and uncheck all checkboxes except "With attach greater than" and enter 1 in the field to the right of it. All attachments will now be displayed. Save them locally and then delete the attachment. Create a new entry of type "Document" and insert the saved attachment there.

Repeat this process until all attachments are available as documents.

Especially for databases with many attachments, this cleanup can lead to massive performance gains.

3) History

Disable password history if you don't actually need it. To do this, click on Properties/Advanced and deactivate "Save history of password changes".

4) Compression

Consider compressing the database.

Compression/decompression requires additional time for loading/saving.

We recommend the following:

  • for local databases - do not use compression
  • for Cloud Databases - Use Compression
  • for databases on the server - compression can be useful for large databases. For smaller systems there are hardly any performance advantages.


 To enable compression, go to Properties and enable "Use compression to reduce database size".

1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.