OpenEdge Data Management: DataServer for Microsoft SQL Server

Table 9: MS SQL Server data type equivalents in OpenEdge (3 of 3)
datetimeoffset 4 DATETIME-TZ
(DATETIME)
(DATE)
(CHARACTER)
binary CHARACTER
varbinary CHARACTER
varbinary(max) 5 CHARACTER
BLOB 6
image 2 CHARACTER
BLOB 6
bit LOGICAL
timestamp CHARACTER 7
identity 8
uniqueidentifier CHARACTER 7
Depends on underlying type 7
computed columns Depends on underlying type 7
cursor Not supported 9
sql_variant Not supported 9
geometry Not supported 9
geography Not supported 9
hierarchyid Not supported 9
Data types
MS SQL Server data type OpenEdge data type equivalent 1
1. The initial entry identifies the default data type. Data types in parentheses identify supported options.
2. Starting in MS SQL Server 2005, legacy "image" and "text" LOB types on the server can be expressed
as BLOB and CLOB types respectively. While still supported, Progress recommends legacy LOB types be
converted to varbinary(max) and varchar(max) types for better forward compatibility.
3. The default CHARACTER mapping for binary LOB server types can be changed to OpenEdge CLOB by
selecting the CLOBs checkbox on the Default to OpenEdge LOB for option during object selection on
schema pull. Changing the mapping from OpenEdge character to OpenEdge LOB may require code
changes. However, Progress recommends mapping MSS character LOB types to OpenEdge CLOBs for
better scalability.
4. Starting in MS SQL Server 2008 using native drivers, these data types can be pulled into an OpenEdge
schema holder for MS SQL Server.
5. The FILESTREAM variant of varbinary(max) data type is also supported.
6. The default CHARACTER mapping for binary LOB server types can be changed to OpenEdge BLOB by
selecting the BLOBs checkbox on the Default to OpenEdge LOB for option during object selection on
schema pull. Changing the mapping from OpenEdge character to OpenEdge LOB may require code
changes. However, Progress recommends mapping MSS binary LOB types to OpenEdge BLOBs for
better scalability.
7. These non-updatable columns can be mapped into an MSS DataServer schema holder but cannot be
written to on the server.
8. You can add an identity data type to a table if you have not already set the PROGRESS_RECID
column to the table's identity column. You can only use the PROGRESS_RECID identity column if you
want to set an identity column for ROWID designation in your OpenEdge file schema. identity
columns created by the user cannot be designated for OpenEdge ROWID or used as part of an index
composite that designates ROWID.
OpenEdge Data Management: DataServer for Microsoft SQL Server 73