OpenEdge Data Management: DataServer for Microsoft SQL Server

Chapter 7: The DataServer Tutorial
3. Select the table for which you are defining a primary key constraint definition and
click Create Constraints. The Create Foreign Constraint Definitions for
tablename dialog box appears, as shown in Figure 16.
Figure 16: Create Foreign Constraint Definitions for tablename dialog
box
4. Accept the default constraint definition name, or enter a new one.
5. Select an index for the primary key constraint definition. Only indexes with an I in
the All Columns Mandatory column are recommended for the primary key
constraint definition. As long a column is unique, you can select as the primary
constraint. Note, however, that the columns designated as the primary constraint
are migrated as NOT NULL capable. That is, if you store many records in your
OpenEdge database with the unknown value, they cannot be migrated to the
foreign data source, given the defined primary constraint on that server object.
6. By default, the primary key constraint definition has the Active check box
selected. Leave this box selected if you want the constraint definition you are
defining to be available for migration.
7. For the DataServer for MS SQL Server, if no clustered index constraint definition
is currently defined, the Clustered check box is selected. Leave selected if you
want the clustered index constraint definition to also be applied to the index you
are selecting for the primary key constraint definition.
Note: Progress Software Corporation recommends defining primary and
clustered constraint definitions for the same index whenever possible.
8. Optionally, add a description of the constraint definition in the Description box.
9. Click OK to save the constraint definition and exit the dialog box.
10. Click Create to save the constraint definition and remain in the dialog box and
continue defining constraint definitions for the selected table.
282 OpenEdge Data Management: DataServer for Microsoft SQL Server