Introduction

If you want to change your used DB System in custo diagnostic you have to move migrate the custo diagnostic Database database to another DB Systemsystem. This can be necessary if your custo diagnostic Database database exeeds the 10 GB limit and you use an Microsoft SQL Server Express.
For this procedure you have to use the Database Converter. For the Database Converter no separate Software software is necessary. The Database Converter is built in the custo diagnostic server.
This procedure is not suiteable Note: You can use this procedure also if you want to move your custo diagnostic Database to another Computer (computer with another or the same DB System).system. (Example: local MariaDB → MariaDB on dedicated Computer)

Preparation

To move migrate the custo diagnostic Database database to another DB System you have to prepare your setup to this situation:

• running custo diagnostic System connected to the previous DB System
• custo diagnostic server Version must be at least 5.1.0
• installed, running and configured new DB System system with empty custo diagnostic Databasedatabase

Its not necessary to prepare a separate cst File file folder because the cst Files files will not be movedmigrated.

...

Migrate the Database

1. Create a copy of the "diag.properties" File
   The "diag.properties" file contains the database connector. The "diag.properties" File file is located in the Folder folder "<diag server Root>\conf". Rename the copied File file to "diag.properties.old".
    
2. Reconfigure your custo diagnostic server to the new DB Systemsystem.
   You can do the reconfiguration by manual if you rewrite the DB connector in the "diag.properties" file.
   As an alternative you can uninstall the custo diagnostic server and reinstall with other DB System system settings. You can use this alternative if you want to use the custo diagnostic database on the same computer. This procedure creates the destination "diag.properties" File which is to be used afterwards.
   Please Note: If you uninstall/reinstall the custo diagnostic server you have to backup and restore the "diag.properties.old" file.
    
3. Please check that your setup is running with the new DB System.
   Please Note Note: Don't create any new Patients or Evaluationspatients or evaluations at this time!
    
4. Stop the custo diagnostic server (stop the Apache Tomcat Windows Service). This prevents changes in the database while migrating.
   Please note: The database server (MariaDB or MS SQL) must be keep running. Its doesn't matter if its the source or target database server.
    
5. Please check that the "diag.properties" and "diag.properties.old" Files files are available in the "<diag server Root>\conf" Folderfolder
    
6. Run the DatabaseConverter Database Converter Script
   1. Open a Command Line Windowcmd
   2. Change the active Folder folder to "<diag server Root>" (Default: "C:\Program Files\custo diagnostic server")

   3. Insert this Code and execute:

      Code Block
      .\jre\bin\java.exe -classpath "webapps\diag\WEB-INF\classes;webapps\diag\WEB-INF\lib\*" de.customed.orm.convert.DatabaseConverter --source=conf\diag.properties.old --destination=conf\diag.properties -Xmx6g

      
      

7. Wait until the system prompt comes back. During the copy procedure the command line window will display all copy steps.
    
8. Start the custo diagnostic server (start the Apache Tomcat Windows Service)Check if all Data is available
    
9. Open the custo diagnostic client and check that all data is available.

Troubleshooting

Process freeze during convert

If the converting process freezes during the processing you can play around with the maximum allocated memory for the java process. With the parameter "-Xmx6g" you can allow to allocate 6 GB at maximum of RAM to the java process. This is normally enough for average sized databases. If you have bigger sizes of databases you can grow this value up to the available physical RAM in your computer.