coDiagnostiX Knowledge Base

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Convert from BDE to SQLite ======

With coDiagnostiX 9.8, the storage system used for patient data has changed.

Why we did this:

  - Ready for data generated by current technology
  - Foundation for future developments
  - The new database is easier to maintain
  - Less prone to harmful user interventions
  - No interference with 3rd party software

However, to profit from the benefits of the new database system, all patients from the 9.7 database need to be moved to the new system. Generally, this process does not require any user intervention. However, in some circumstances, questions may arise. This article is intended to answer these questions.

===== The conversion process =====

Converting an old database into the new structure happens without requiring user intervention. The process can be separated into two phases:

  - Creation of the patient index
  - Conversion of the patient datasets

==== 1. Creation of the patient index ====

This happens nearly instantly. In most cases, the user can continue working after a few seconds.

Technically, the following happens:

  - When starting version 9.8 with a 9.7 database, the user is asked if he wants to convert the database or would rather create a new one.
  - If the database should be converted coDiagnostiX first moves the old database into a subdirectory of the database path. Example: If the database is at "C:\Database\", it is moved to "C:\Database\Legacy\"
  - coDiagnostiX then creates a new empty database and reads the list of patient datasets from the old database. All datasets remain in the old database.

==== 2. Conversion of the patient datasets ====

When the user opens a planning, all datasets of the patient are read from the old into the new database. Depending on the number of datasets, plans and planning objects like model scans and drill guides, this can take from about ten seconds up to several minutes.

When the planning is displayed on the screen, the conversion is done. The patient is now completely stored in the new database //and// the old database. Currently, the patient is never deleted from the old database. This will change in a future update of coDiagnostiX. It is planned to delete patient data which has completely been moved to the new database.

===== Compatibility =====

coDiagnostiX 9.8 is able to read databases created with coDiagnostiX down to version 9.0.2. Older databases must be opened first with a coDiagnostiX version between 9.0.2 and 9.7.6.
Versions of coDiagnostiX older than 9.8 are not able to read patient datasets created with coDiagnostiX 9.8 or newer.

This concerns:
  * Databases
  * Cases on caseXchange
  * Cases on the SQL network database
  * Archive files
  * Exported plans

==== caseXchange ====
{{ :database:database_cxcoldversion.png|}}

Datasets sent from version 9.7 or older can be received from version 9.8 without further notice. Version 9.7, however, is not able to receive data sent from 9.8.

  * While the data is sent to the recipient, the sender will receive the information that the receiver uses an old version of coDiagnostiX and will not be able to read the data until the installation is updated.
  * The recipient will see the case in his inbox along with the information that he needs to update first before being able to download the case.

==== SQL network database ====

Unlike the local database, the SQL network database can still be accessed by older versions of coDiagnostiX. Datasets are converted case by case into the new data format by the coDiagnostiX client when adding or checking-in data to the SQL network database. The individual dataset can only be read by coDiagnostiX 9.8 or newer.

===== Database folder structure =====

  Database
  |-Cache
  |-Legacy
  |-Patients

==== Database ====

PatientDatabase.cdxDatabase is the only permanent file in this folder. It is an index file and contains the patients' meta data, like names, date of birth and the hospital's patient id.

==== Cache ====

The directory contains one cache file for each patient dataset in the database. These files contain data required to visualize (CB)CT data. If disk space is required, these files can be deleted. They are recreated when the corresponding patient dataset is opened the next time.

==== Legacy ====

**Do not change anything in this folder.** It will very likely make the contained patient data unreadable.

This folder contains the old BDE database. Whenever a patient dataset is opened that was not opened in version 9.8 (or newer) before, the dataset is read from the BDE database and stored in the new database.

==== Patients ====

This directory contains one file for each patient in the database. A cdxPatient-file contains all data that belongs to a patient. The includes (CB)CT data, plannings, imported model scans and planned implants.
===== Parallel usage of pre 9.8 versions with 9.8 or later versions =====

While installing different versions of coDiagnostiX in parallel is possible, it is not recommended. However, measures have been taken to make this as easy as possible.

  * When updating to version 9.8, the database path of version 9.7 is changed to a new, not existing database path. Name: [database path] + "97". When version 9.7 is started, it will create a new, empty database in that folder.
  * Using the BDE database in the legacy folder inside of a converted database with a parallel installation of 9.7 is not recommended. Instead, the old database should be copied **before** the conversion.
  * Datasets already converted to version 9.8 should be removed from the copy to avoid confusion.
  * Having an SQLite (9.8 and newer) and a BDE (9.7 and older) in the same directory should not be a problem. Version 9.8 will first try to find a SQLite database in that directory and open it. A BDE database is only opened and converted if no SQLite database can be found.

===== Downgrade of a 9.8 database to 9.7 =====

Not possible.