OpenEdge Data Management: DataServer for Microsoft SQL Server

Creating a schema holder
You can select tables based on the object name, owner information, and qualifier.
For example, you can specify A* in the Object Name field to list all the tables
whose names begin with A or a.
Note: You should not specify an entry that consists exclusively of wild cards for
each of the three entry fields in the dialog box. An entry that consists
exclusively of wild cards might degrade the performance of the database
when you perform a schema pull. (It will include system catalog files from
the data source not typically included in user databases.)
Check Default to OpenEdge DATETIME to automatically map MS SQL Server
data types to the associated OpenEdge data type. If you have modified your client
application to handle LOB data types, check Default to OpenEdge LOB for:
CLOBs and/or BLOBs to map the OpenEdge LOB data type to MS SQL Server
VARBINARY(MAX), IMAGE and FILESTREAM data types. For more information on
mapping OpenEdge and MS SQL Server data types, see“Support for OpenEdge
ABL BLOB data type” section on page 87. If you select Designate
Primary/Clustered index as ROWID, you will get the warning “Existing ROWID
designations may be overwritten by selecting this option”. If selected, and a given
table has a clustered index and does not have the _PROGRESS_RECID field defined
for it, it will be used as ROWID if it qualifies for ROWID selection. Qualification
requires that the index be unique. This designation for ROWID takes precedence
over any other options selected for the schema pull operation but does not
overwrite a legacy ROWID designation that is based on the presence of
_PROGRESS_RECID. When the Select ‘Best’ ROWID Index is selected during
migration, this option provides the legacy equivalent of ROWID designation
behavior in prior versions where the PROGRESS_RECID column was not present in
a table. When selected in conjunction with new process flow options for ROWID
migration, this option plays a secondary role in the designation of ROWID indexes
deferring to the Designate Primary/Clustered index as ROWID option as the
first choice. This option searches for a viable index for ROWID when an
_PROGRESS_RECID column does not exist and other process flow options that take
precedence do not render a viable index.
Note: The Designate Primary/Clustered index as ROWID option may produce
some or all of the “natural” key selections available from the foreign table's
indexes. These can be considered alternatives to the PROGRESS_RECID column
or other ROWIDs previously designated.
OESchema allows you to locate as ROWID if it meets the requirements of the OE
Schema. The OE Schema criteria is described in the “Best index selection”
section on page 263. If a Best index selection can be found in the OE Schema, it
is designated as ROWID. When this option is used in conjunction with the
Designate Primary/Clustered index as ROWID option, this option specifies a
secondary path in the search for the designated ROWID index. The primary and
clustered selections associated with those options will take priority in ROWID
selection as does the presence of a _PROGRESS_RECID column. Select Foreign
Schema option to locate an existing index to use as ROWID from the ODBC API
that evaluates best index on the server. If a Best Index selection can be found
through the ODBC API, it is designated as ROWID. When selected, this option
warns you that “Existing ROWID designations may be overwritten by selecting this
option”. If this option is selected in conjunction with the Designate
OpenEdge Data Management: DataServer for Microsoft SQL Server 267