OpenEdge Data Management: DataServer for Microsoft SQL Server

Managing server attributes
Defining constraint definitions in Data Administration
Use the procedures described in the following sections to define constraint definitions
in Data Administration:
• Defining a primary key constraint definition
• Defining a unique key constraint definition
• Defining a foreign key constraint definition
• Defining a check constraint definition
• Defining a default constraint definition
The dialog boxes for defining primary, unique, and clustered index constraint
definitions contain a common section that displays current settings for both OpenEdge
properties and defined constraint definitions, a sample of which is shown in Figure 15.
Figure 15: Index properties
Possible values for each field are:
• C — A C in a column indicates that a constraint definition of this type is currently
defined. The constraint definition can be created in the foreign database if you
configure your migration to migrate constraint definitions.
• I — An I indicates that the property is currently defined your OpenEdge database.
Defining a primary key constraint definition
The following procedure describes how to define a primary key constraint definition.
To define a primary 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.
OpenEdge Data Management: DataServer for Microsoft SQL Server 281