hexagon logo
Register Sign in

Q-DAS Database Management when using the Microsoft SQL and Oracle

This topic provides guidance on managing and handling Q-DAS databases when used with Microsoft SQL or Oracle database management systems.
Due to the varying database structures required for different purposes, the Q-DAS applications need four different types of databases to work properly. The required database can be empty, or a suitable existing database can be used to which the relevant Q-DAS structure can be added.
Link to: Details on required databases for different Q-DAS database types
Each process is explained using brief steps with links to in-depth guidance covering all important information.

Table of Contents

Create Microsoft SQL or Oracle databases after the Q-DAS installation process

Create Microsoft SQL or Oracle databases before the Q-DAS installation process

Update Microsoft SQL or Oracle databases before the Q-DAS update/upgrade installation process

Transferring databases from Microsoft Access to other database management systems

When initially working with Microsoft Access databases and later deciding to switch to a different database management system, it is possible to transfer the data from Microsoft Access to the Microsoft SQL or Oracle.

The first step is to identify which Q-DAS database types are used with Microsoft Access. The Q-DAS applications need four different types of databases to work properly. This is mainly due to the varying database structures required for different purposes.
- Text: Contains all texts in all languages for the Q-DAS system.
- Configuration: For the settings of the Q-DAS system.
- Licence: For the licence information.
- Data: The measured value databases. Depending on the installed products and the applied data flow, different measured value databases may be in use. For example, the buffer and central databases when using O-QIS MCA/CMM Reporting.

The Database Connect tool (FD Connection Tool) can be used to get an overview.
Link to: Management tool for the database connections used by Q-DAS applications

Text database type

  • Ensure that a database for TEXT has been created on the relevant database system.
  • Check if any changes have been made to the database. This may include modified content or individual text.

    No changes
  • Use "Static DB" tool to create a new database, the structure and the content, for the required Q-DAS database type TEXT.
    Link to: How to create Q-DAS database structure for new Microsoft SQL and Oracle databases
    When transferring a database involving a major or minor upgrade, ensure that the corresponding "Static DB" version matches that of the Q-DAS applications.
    Link to: Launching "Static DB" tool
  • Close all Q-DAS applications and launch the "Database Connect" tool. Change the existing text database connection from Microsoft Access to the new database. In a default installation, this is database connection named QDAS_TEXT_001. This ensures that all Q-DAS applications use the new text database without the need for modifications to individual product INI files.


    If  if any changes have been made to the database, the text database requires an update
  • Launch a Q-DAS Application, for example qs-STAT and go to
    <File> | <Configurations> | <Databases> | <Options> | <Administration> | <Copy text and config. Database> | <Target database for configuration>
    Link to: Database Administration - Settings and Options
    Brief summary of the steps:
    - Create new database connection (FD) for the empty database and press create database. The structure and content from the Microsoft Access database will be created and copied to the new database.
    - Close the Q-DAS Application and launch the "Database Connect" tool. Change the existing text database connection from Microsoft Access to the new database. In a default installation, this is database connection named QDAS_TEXT_001. This ensures that all Q-DAS applications use the new text database without the need for modifications to individual product INI files.
  • If a major or minor update is to be carried out, use the "Database Update" tool to add the text content of the new Q-DAS versions.
    Link to: "Database Update" tool

Configuration database type

  • Ensure that a database for CONFIGURATION has been created on the relevant database system.
  • Launch a Q-DAS Application, for example qs-STAT and go to
    <File> | <Configurations> | <Databases> | <Options> | <Administration> | <Copy text and config. Database> | <Target database for configuration>
    Link to: Database Administration - Settings and Options
    Brief summary of the steps:
    - Create new database connection (FD) for the empty database and press create database. The structure and content from the Microsoft Access database will be created and copied to the new database.
    - Close the Q-DAS Application and launch the "Database Connect" tool. Change the existing text database connection from Microsoft Access to the new database. In a default installation, this is database connection named QDAS_CONF_001. This ensures that all Q-DAS applications use the new configuration database without the need for modifications to individual product INI files.
  • If a major or minor update is to be carried out, use the "Database Update" tool to add the default configuration for new graphics and functions.
    Link to: "Database Update" tool

Licence database type

Note: Never change the type, location or name of the licence database, the name or IP address of the database server or uninstall the Q-DAS products while the licences are still registered. First, release the licences by deregistering the products.
Therefore, a licence database can never be "moved". Instead, a new licence database needs to be created and product registration needs to be carried out again.

  • Ensure that a database for LICENCE has been created on the relevant database system.
  • Use "Static DB" tool to create the structure for the required Q-DAS database type LICENCE.
    Link to: How to create Q-DAS database structure for new Microsoft SQL and Oracle databases
    When transferring a database involving a major or minor upgrade, ensure that the corresponding "Static DB" version matches that of the Q-DAS applications.
    Link to: Launching "Static DB" tool
  • Release the licences by deregistering the products using the "Q-DAS License" tool.
    Link to: "Q-DAS License" tool
  • Launch the "Database Connect" tool. Change the existing licence database connection from Microsoft Access to the new database. In a default installation, this is database connection named QDAS_LIC_001.
  • Relaunch the "Q-DAS License" tool. It will now use the new database.
    Register the licence for use with this new licence database.

Data database type (measured values)

The value databases are transferred via an export.

  • Ensure that a database for DATA has been created on the relevant database system.
  • Use "Static DB" tool to create the structure and default content for the required Q-DAS database type DATA.
    Link to: How to create Q-DAS database structure for new Microsoft SQL and Oracle databases
    When transferring a database involving a major or minor upgrade, ensure that the corresponding "Static DB" version matches that of the Q-DAS applications.
    Link to: Launching "Static DB" tool
  • Launch the "Database Connect" tool. Create new FireDAC database connection for the new DATA database that has been created on the relevant database system.
    Link to: Management tool for the database connections used by Q-DAS applications
  • Launch a Q-DAS Application, for example qs-STAT and go to
    <File> | <Configurations> | <Databases> | <Options> | <Administration>
    Link to: Database Administration - Settings and Options 
    While some of the settings in this dialogue box are saved to the value database, others are saved under configuration. Therefore, check and document all settings in this dialogue box. For example, take screenshots to use for comparison with the new value database at a later stage.
    Note: Since additional data fields are stored in the value database, it is important to configure them in the new database in the same way.
  • If catalogue data from a database is being used, it needs to be exported so that it can be transferred to the new value database at a later stage.
    Link to: Overview of the catalogue functions
  • Check if the data recording involves filling in incomplete measured values.
    When the "Rearrange subgroups" (K0080/81) option is used for data recording, or the "Fill in not recorded characteristics" option is used for part measurements, any gaps in the data are marked with an attribute. 
    To prevent "data gaps" from being lost during the transfer process, and thereby maintain the integrity of the data structure, the "Sort and fill by serial number" option needs to be enabled before exporting. 
    <File> | <Configurations> | <Databases> | <Options> | <User Options> | <sort> | <Sort and fill by serial number> 
    Link to: Database Administration – User Options

  • Export datasets as DFQ files.
    This is done by selecting all the required datasets in the "Read from database" dialogue box. Then, select the "Save dataset to files" option from the context menu. This will open the export dialogue box.

    Note: Not all available information is included when data sets are saved as files. The following information will be lost during export:
    - Information for digitally signed values (WVLOCKED)
    - Allocated documents
    - Allocated images
    - Data amendment log
    - Parent-child structures
    - Drawing files (images) stored in the database

  • Change the value database connection to the new value database within a Q-DAS Application, for example qs-STAT.
    <File> | <Configurations> | <Databases> | <Q-DAS Database>
  • Compare and modify the database administration options with those of the Microsoft Access database. For example, if screenshots were taken, use these to make a comparison.
    For the new value database, it is important that the same additional data fields are enabled as in the Microsoft Access value database.
    <File> | <Configurations> | <Databases> | <Options> | <Administration>
  • Save the DFQ files as datasets in the new value database.
    This can be achieved by loading and saving each file individually to the database.
    <File> | <Save...> | <Save to database> when the file is loaded.
    Alternatively, Q-DM (Upload) can be used to upload all files to the database at once. A licence is required to use Q-DM.
  • Set the database connection used by the Q-DAS application back to its original database connection name. Change the value database connection from the new value database back to Microsoft Access value database. 
    <File> | <Configurations> | <Databases> | <Q-DAS Database>
  • Close all Q-DAS applications and launch the "Database Connect" tool. Change the existing value database connection from Microsoft Access to the new database. In a default installation, this is database connection named QDAS_DATA_001. This ensures that all Q-DAS applications use the new value database without the need for modifications to individual product INI files.
Related
Recommended
© 2026 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement