This section describes how to create a relational MR database from a Quanvert database using the new RDB DSC 2. However, the process may not be suitable for some Quanvert databases, particularly if they are very large.

The steps are:

1: Preparing the Quanvert database

2: Creating the .mdd file

3: Creating a new SQL Server database

4: Exporting the Quanvert data to the new database

5: Changing the default data source

Quanvert axes usually contain various special elements that define special summary and statistics rows and intermediate values that are used during tabulation. Quanvert DSC creates two columns in the virtual table for categorical variables that contain these types of special elements. The first (called varname, where varname is the axis name) stores the responses to the categories and the second (called varname.ex) stores the data for the special elements.

If you examine the data in the database after converting a Quanvert database to a relational MR database, you will see these additional .ex variables. Some UNICOM Intelligence products, such as UNICOM Intelligence Reporter, recognize the special elements and recombine the two variables when reading a Quanvert database. However, this may not happen when reading a relational MR database and you may therefore see additional .ex variables listed in the list of variables, and so on. However, you can use the standard variables in the normal way. For more information, see Quanvert DSC.