OpenEdge Data Management: DataServer for Microsoft SQL Server

Preparing to create demonstration databases
Table 7–1: OpenEdge DB to MS SQL Server utility (2 of 2)
Interface element Description
Include Defaults Check if you want the OpenEdge initial value used
as the default in the SQL script.
For field widths use When pushing fields to a foreign data source, you
can select one of two primary field format options:
• Width — Uses the value of the _width field
in the _field record.
• 4GL Format — Compiles with the current
default width specified. (default)
If you select the 4GL Format option, you
have an additional setting to define:
• Expand x(8) to 30 — This setting is on by
default to indicate that the format for the
character fields defined as x(8) will be
created as 30 characters.
Note: For a complete description for running while in batch mode, see the “Running the
OpenEdge DB to MS SQL Server utility” section on page 7–20.
10. Running the utility creates and connects a schema holder and the MS SQL Server
database. It operates as follows:
a. SQL script is generated.
b. SQL that creates the schema is sent to the MS SQL Server data manager.
c. The schema is pulled back to the schema holder.
d. The schema holder and the OpenEdge database are compared and all information
needed by OpenEdge is applied to the schema holder.
e. Data is loaded if selected.
f. The schema holder is disconnected.
Note: You cannot use the Expand x(8) to 30
setting with the Width option.
For Create RECID use: Select either Trigger or Computed Column.
Trigger is selected by default. Computed
Column is preferred as it offers greater reliability,
but is only available for MS SQL Server 2005 and
later.
g. A message is displayed that tells the user which startup procedure to use to connect.
Additionally, the entered connect information is also stored in the db record which
the DataServer can use to automatically connect.
7–5