OpenEdge Data Management: DataServer for Microsoft SQL Server

Chapter 7: The DataServer Tutorial
Table 52: OpenEdge-to-MS SQL Server Conversion utility batch
parameters (2 of 3)
Environment
variable Description
MAPSMSSDATETIME Specify if new date and time data types should be used
(set on only for MS SQL Server 2008 or above).
VARLENGTH Total number of characters a VARCHAR can have. Any
field whose format is greater that will be defined as a text
field. Maximum is 8000.
SQLWIDTH If present, use the OpenEdge file _WIDTH field size
instead of calculating length by using the display format.
LOADSQL Allows you to specify whether you want the utility to
create the schema in your empty MS SQL Server
database. Specify YES to enable this behavior.
MOVEDATA Allows you to specify whether to populate the database.
Specify YES to dump and load data or NO to not
populate the database. For example, you might specify
NO if your database is large, and you want to dump and
load data at a more convenient time. The default is NO.
UNICODETYPES Sets to YES to use Unicode types, and NO otherwise.
The default is NO.
UNICODE_EXPAND Set to YES to double the length of fields on conversion,
and NO otherwise. The default is NO.
MIGRATECONSTR Migrates constraint definitions from the OE database
definitions to the foreign data source and schema image.
MAPOEPRIMARY Determines whether the OE primary will be mapped to
SQL Server and utilized for the clustered index and
ROWID defaulting scheme.
EXPLICITCLUSTERED Determines if the migration should be explicit or implicit
while trying to produce a clustered index before it targets
the ROWID candidate.
GENROWID
or
COMPATIBLE
Determines if the migration should attempt to generate
table definitions that provide compatibility with
OpenEdge ROWID. Previously, the ROWID was
resolved by adding table definitions (when
COMPATIBILE=YES) or by using a "best index" selection
algorithm (when COMPATIBLE=NO).
GENRECID/COMPATIBLE extends the options,
MAPOEPRIMARY and EXPLICITCLUSTERED to generate a
OpenEdge compatible ROWID solution irrespective of
the way OpenEdge primary indexes map to tables
processed by the migration.
This option is active by default. If you use COMPATIBLE
the new changes are fully consistent with the old
migration option and do not result in change in the old
default behavior.
300 OpenEdge Data Management: DataServer for Microsoft SQL Server