Create Composite KeysUse the Client Configurator to create composite keys if unique keys haven't been specified in the DMSII data. A composite key is created from a set of column names in a table that's derived from a data set. If unique keys are not defined and you use Unisys Enterprise Database Server for ClearPath Extended Edition (formerly known as DMSII Extended Edition), the DATABridge Client creates unique keys using RSNs, because they provide the best indexes. If RSNs aren't available, valid AA values are used for keys. This means that if a DMSII reorganization occurs, you will need to reclone all of your data sets. In data sets that don't have fixed length records, the AA values continually change and cannot be used as keys. Caution: Before you create keys, make sure that your key (the combination of columns) will be unique and will not encounter duplicates. Otherwise, your data can become corrupted. You can only create composite keys for uncloned data sources. Create a unique composite key
| ||
|