OpenEdge Data Management: DataServer for Microsoft SQL Server

Processing activities that require additional action
Data types
The following processing activities require the defined action to successfully convert
existing 32-bit INTEGER columns to 64-bit INT64 columns:
• When existing r-code references a column’s original 32-bit INTEGER definition,
you must recompile the code and check the table’s Cycle Redundancy Check
(CRC).
• Contrast the actions required to perform the following data definition changes:
– If you change data definitions in your original OpenEdge database from
INTEGER to INT64 and you had previously migrated your database to either
a MS SQL Server or an ODBC DataServer, you must repeat the migration
step to change the field’s physical storage on the foreign data source.
– If you change data definitions in your original OpenEdge database from
INT64 to INTEGER and you had previously migrated your database to either
a MS SQL Server or an ODBC DataServer, you must repeat the migration
step to change the field’s physical storage on the foreign data source, and
then dump and reload the field’s data.
• If you changed your native definition to include a bigint data type, it is
recommended that you repeat the step to pull the table into your schema holder.
Otherwise, a conversion from the native bigint data type might occur at run-time
if your schema holder defines a different data type. Also, if the schema holder
definition of the native bigint is INTEGER, an overflow condition might occur when
accessing data in the foreign data source.
Determining your application needs
Determine your application needs and goals before changing INTEGER data types to
INT64 data types in applications. Not all INTEGER data types will necessarily require the
additional bit size, nor will wholesale changes in data types necessarily work efficiently
with other interfaces to ABL. For more information about determining when to use
INT64 versus INTEGER, refer to the Release 10 ABL Data Types Web paper available
at the Web paper category of the PSDN Web site located at
http://communities.progress.com/pcom/community/psdn.
OpenEdge Data Management: DataServer for Microsoft SQL Server 75