Reconfiguring a Single Database
- Last UpdatedFeb 15, 2023
- 2 minute read
The simplest reconfiguration involves a single Database (DB) which has no references into it from other DBs; for example, a Model DB which has no associated Drawing (PADD) DBs.
A simple reconfiguration requires a source and a destination DB. When the process has been completed, the source DB will remain unchanged, and the destination DB will contain a compacted copy of the parts of the source which were specified in the copy list.
The transfer of data takes place in two passes, the second of which is further divided into two phases:
|
PASS 1 |
The data is read from the source DB and written to a pair of intermediate files. The first file holds the element structures and the non-reference attributes, the other holds the reference attributes. |
|
PASS 2 - Phase 1 |
The first file is read by the RECONFIGURER and used to recreate the original structures in the destination DB, including setting of the non-reference attributes. |
|
PASS 2 - Phase 2 |
The second intermediate file is read and its contents used to set all reference attributes in the destination DB and to perform insertion operations. |
The reason for the two phases is that references in the source DB may refer to elements lower down in the hierarchy. It is necessary, therefore, to create all elements in the destination DB before trying to set references to any of them.
Since the two passes perform independent and consecutive operations, the process can be interrupted after PASS 1 has been completed, with PASS 2 being run later.
The reconfiguration has four basic steps:
-
Specify where the data to be reconfigured is coming from.
-
Specify where the reconfigured data is going to.
-
Specify which parts of the source data are to be copied to the destination.
-
Start the reconfiguration process.