OpenEdge Data Management: DataServer for Microsoft SQL Server

Managing server attributes
If the primary constraint definition is incorrectly defined, a message is displayed
and the constraint definition is not created.
The system fails to generate a constraint definition when an index is not defined
as unique by the presence of either an OpenEdge unique attribute (indicated by
an I) or by a unique constraint definition (indicated by a C) in the Unique column.
Defining a unique key constraint definition
The following procedure describes how to define a unique key constraint definition.
Alternately, you can define unique constraint definitions during migration.
To define a unique key constraint definition:
1. Start Data Administration and connect to the OpenEdge database you are
migrating.
2. Select DataServer→ MS SQL Server Utilities→ Server Attributes→
View/Maintain Foreign Constraints. The View/Maintain Foreign Constraint
Definitions dialog box appears.
3. Select the table for which you are defining a unique key constraint definition and
click Create Constraints. The Create Foreign Constraint Definitions for
tablename dialog box appears, as shown in Figure 16.
4. Select UNIQUE from Constraint Type. The appearance of the Create Foreign
Constraint Definitions for tablename for a unique key dialog box, appears as
shown in Figure 17.
Figure 17: Create Foreign Constraint Definitions for tablename dialog
box for unique constraint definitions
5. Accept the default constraint definition name, or enter a new one.
6. Select an index for the unique key constraint definition.
OpenEdge Data Management: DataServer for Microsoft SQL Server 283