Microsoft Azure Synapse SQL Connector

Back Next

Microsoft Azure Synapse SQL and transformation data types

The following table compares the

Microsoft Azure Synapse SQL

native data type to the transformation data type:

Microsoft Azure Synapse SQL Data Type	Transformation Data Type	Range and description
bigint	bigint	-9,223,372,036,854,770,000 to 9,223,372,036,854,770,000
binary	binary	1 to 8000 bytes
bit	integer	0,1,NULL
char	string	1 to 8000 characters
date	date/time	January 1, 1753 00:00:00 to 12/31/9999
datetime	date/time	January 1, 1753 00:00:00 to December 31, 9999 23:59:59.997
datetime2	date/time	1 to 8000 characters When you create a mapping in advanced mode, the fractional seconds in the datetime2 fields are written only up to 6 digits in the target.
datetimeoffset	string
decimal	decimal	Number with 28-bit precision and scale 0 to 5 for mappings. When the table has a defined decimal column with precision more than 28, but the table contains data less than 28, Data corruption might occur. Number with 38-bit precision and scale 0 to 5 for mappings in advanced mode.
float	decimal	Precision 7, scale 0 to 7
int	integer	-2,147,483,648 to 2,147,483,647
money	decimal	-922,337,203,685,477.0000 to 922,337,203,685,477.0000
nchar	string	1 to 8000 characters
nvarchar	string	1 to 4000 characters
real	double	Precision 7, scale 0 to 7
smalldatetime	date/time	1/1/1900 0:00 to 6/6/2079 23:59
smallint	integer	-32,768 to 32,767
smallmoney	decimal	-214,748.3648 to 214,748.3647
time	string	00:00:00.0000000 to 23:59:59.9999999
tinyint	integer	0 to 255
Uniqueidentifier	string	0 to 36 characters
varbinary	binary	1 to 8000 bytes
varchar	string	1 to 8000 characters

Binary and Varbinary data types are not applicable for mappings in advanced mode.

The

datetimeoffset

data type is supported only for passthrough mappings that read data from and write data to

Microsoft Azure Synapse SQL

objects.

When you read or write varchar or nvarchar data types, do not use

character in the string data.

When you create a new target, the fields of Uniqueidentifier data type in the source are converted to Nvarchar data type in the target.

To retain the Uniqueidentifier data type, edit the metadata for the target fields and change the native type of the fields to Uniqueidentifier.