Database Ingestion and Replication

Back Next

Oracle Source and Microsoft SQL Server Target

The following table identifies the recommended data-type mappings for

configurations with an Oracle source and a SQL Server target:

Oracle Source Data Type	SQL Server Target Data Type
binary_double	float
binary_float	real
blob	varbinary
char	varchar
clob	varchar
date	datetime2
float	varchar
long raw	varbinary
long	varchar
nchar	nvarchar
nclob	nvarchar
number	One of the following types: decimal, 1 <= p <= 38 and s >= 0 and s <= p money, s > p or s < 0, number of digits and scale can be accommodated bigint, s <= 0, storage size can be accommodated char
nvarchar2	nvarchar
raw	varbinary
rowid	varchar
timestamp	One of the following types: datetime2, fraction seconds <=7 char
timestamp with time zone	One of the following types: datetimeoffset , fractional seconds <=7 char
varchar2	varchar
xml	varbinary(max)

LOB limitations

Database ingestion and replication

initial load, incremental load, and combined load jobs can replicate data from Oracle BLOB, CLOB, NCLOB, LONG, LONG RAW, and XML columns to SQL Server targets. LOB column data might be truncated on the target. The truncation point depends on the data type and target type. For all of the Oracle LOB data types and this target, the truncation point is 1677721 bytes. For more information, see the "Include LOBs" description in Configuring the source.

Columns that have the LONG, LONG RAW, and XML data types are supported in initial load jobs and in incremental load and combined load jobs that use the

Query-based

CDC method. However, jobs that use the

Log-based

CDC method do not replicate data from these columns to the generated target table.

Unsupported source data types

Database Ingestion and Replication

does not support the following Oracle source data types with any load type:

"ANY" types such as ANYTYPE, ANYDATA, ANYDATASET

Extended types

INTERVAL

JSON

BFILE type for storing LOB data externally