OpenEdge Data Management: DataServer for Microsoft SQL Server

ntext 9
nvarchar(max)
SQL_NLONGVARCHAR CHARACTER
money SQL_DECIMAL DECIMAL
(INTEGER)
smallmoney SQL_DECIMAL DECIMAL
(INTEGER)
datetime SQL_TIMESTAMP
smalldatetime SQL_TIMESTAMP
Data type conversion details
Table C–1: MS SQL Server data type details (2 of 2)
MS SQL Server data
type
SQL-ODBC 1
data type
CHARACTER 13
(DATE 14 )
CHARACTER 13
(DATE 14 )
binary
7 SQL_BINARY CHARACTER
varbinary SQL_VARBINARY CHARACTER
image SQL_LONGVARBINARY
CHARACTER 12
bit SQL_BIT LOGICAL
timestamp 15 SQL_VARBINARY Unsupported
identity 16 NA Not supported
OpenEdge-equivalent
data types
1. The SQL-ODBC data types demonstrate the mapping of native MS SQL Server data types to the ODBC standard.
2. Existing or new 32-bit INTEGER data types have a maximum internal field size of 64-bits. The internal field
expansion supports larger values defined as INTEGER data types.
3. Numeric expressions supported include DECIMAL, INTEGER, and INT64.
4. The OpenEdge INT64 data type enables the MS SQL Server DataServer BIGINT data type to be successfully pulled
into a schema holder.
5. The DataServer truncates values in MS SQL Server decimal or numeric columns defined with a scale greater than
10. In the case of float columns, it reliably translates up to 10 places only.
6. Do not use the FLOAT or REAL data types in joins, in primary keys, or with the equality operator.
7. When you define a binary or char column to allow nulls, MSS stores the data type definitions as varbinary and
varchar respectively. This does not affect how the DataServer maps the MSS data types to OpenEdge data types.
8. When migrating an OpenEdge database to SQL Server, character fields whose format is less than x(8000) are defined
as VARCHAR by default. Larger character fields are defined as TEXT. If there are several large text fields in one
record that each individually fall under the size limits to be defined as VARCHAR, but in sum exceed the maximum
record size for SQL Server, it will be necessary to define the fields as TEXT to successfully create the records.
9. Text/ntext types changed to varchar(max)/nvarchar(max) in MS SQL Server 2005.
10. The amount of data that can be accessed in a field defined to be TEXT by an OpenEdge application is limited by
the maximum size of a record that can be passed to the client. The maximum is 32K. The performance option
BINDING cannot be used with a TEXT data type. To work around that limitation, construct field lists to exclude the
retrieval of the TEXT data. Starting in MS SQL Server 2005, non-Unicode CLOB types are mapped to varchar(max)
instead of text and Unicode CLOB types are mapped to nvchar(max).
11. Starting in MS SQL Server 2005, CLOB types are mapped to varchar(max) instead of text.
12. Although the MS SQL Server text and image fields can hold up to 2MB, OpenEdge retrieves only up to 32,000
bytes. If you are using an OpenEdge Format phrase, there might be additional limits on the size of text and image
fields. See OpenEdge Development: ABL Reference. You can use the DataServer (-Dsrv
MAX_LENGTH) startup parameter to limit the amount of returned text data.
13. By default, the initial value of a MS SQL Server datetime or smalldatetime column is the Unknown value (?). The
default initial values for binary and varbinary are also the Unknown value (?). The MS SQL Server datetime and
smalldatetime data types contain both date and time information. The DataServer maps these to the OpenEdge
DATE data type; however, you can change the DATE data type to CHARACTER in the schema holder. If you do this,
remember to change the format to match the new data type. For example, if you change the data type to
CHARACTER, specify a character format, such as x(26).
C–3