Creating the Target Version Database

This chapter provides an overview of the process required to create the Progress target version database.

This section provides guidelines on creating the target environment you will need for a buffer copy or in-place conversion. Use these guidelines in conjunction with the instructions in the QAD Standard Edition Installation Guide: Progress Database to install and configure the target QAD Standard Edition environment.

Important: Install your new version to a new directory location. This is especially important if you are converting from a previous version of eB2 because the default installation locations are the same. If you installed eB2 to \mfgsvr, install QAD Standard Edition to a directory such as \qad<yyyy>. The instructions in this document refer to this directory as the target version installation directory (TVInstallDir). The installation guide refers to the same directory as QADInstallDir.

2 Install and configure the database server and at least one character client using the instructions in the installation guide. However, note the following differences between configuring an initial installation and configuring a target version environment for a conversion:

• For all conversions, make sure the target databases have different names than the source databases. This applies to the main and admin databases.

• For buffer copy conversions, when assigning extent sizes for the new databases, be sure to consider the size of the tables in your source version databases.

• For buffer copy conversions, build production, admin, and help databases, but do not load any default system data or run the OID seed program.

• For in-place conversions, the same rules apply, but you also do not build a production database.

• For the help database, you can load the data files in the mfghelp subdirectory to implement the system source code cross-reference feature.

Note: These help data files are for system cross-reference only and do not contain the field and procedure help. The field and procedure help records are loaded in the post-conversion steps.

3 Open these two files in a text editor, and delete the reference to bkd_det. Then save the files.

4 Configure a database set containing the mfgempty, admempty, hlpempty, and audempty databases for the compile.

6 Record the locations of your target version databases and the directory where you installed the target version database server files.