Update Client
Replace the files and folders of your installation of
DiversityCollection with the files you received by e-mail or downloaded
from the DiversityWorkbench portal. The database will not be influenced
by this replacement. After starting the new software you need to
transfer the settings of the previous version. When you start the
program and connect to a database, the program will check if it is
compatible with the database or if the database needs an update. In any
of these cases an
update entry in the menu
will appear. If a new version of the client is available, this menu will
contain an
update client … entry.
Click on it to open the webpage where you may download the client as
shown below.

Update Database
Update database to current version
If you are the owner of the database (Database role = dbo) and the
database needs to be updated, the menu will contain an
update database … entry. Select this entry
to open a window as shown below to run the provided update scripts,
delivered with the client software. These scripts need to run
consecutively, so e.g. to update from version 2.5.1 to 2.5.4 you either
have to run the script DiversityCollectionUpdate_020501_To_020504 or the
scripts DiversityCollectionUpdate_020501_To_020502,
DiversityCollectionUpdate_020502_To_020503 and
DiversityCollectionUpdate_020503_To_020504. The program will guide you
through these steps and check for the scripts. All you need to do is
click the Start update
button.

Update of all databases on a server
If you are database owner and have a windows login to the database server (user=dbo), you have the option to update all DiversityCollection databases on this server by starting the application with command line parameters. Open a command line window, navigate to the program directory and start DiversityCollection with the keyword “UpdateDatebase”, the server name (or IP address) and the port number:
DiversityCollection.exe UpdateDatabase 127.0.0.1 5432
The program will connect to the server and update all available databases to the current version. If you want to exclude dedicated databases from update, create a text file named “ExcludeDb.txt” that contains the excluded database names - each name in a separate line - and locate it in the resources directory. The update will be done in the background without opening a program window. When the update processing is finished, an overview of the performed actions will be written into the protocol file “Updatereport.log” in directory resources/Updates.