Microsoft SQL Server->GaussDB
Data Type (Microsoft SQL Server) |
Data Type (GaussDB) |
Whether to Support Mapping |
---|---|---|
TINYINT |
SMALLINT |
Yes |
SMALLINT |
SMALLINT |
Yes |
INT |
INTEGER |
Yes |
BIGINT |
BIGINT |
Yes |
DECIMAL |
NUMERIC |
Yes |
NUMERIC |
NUMERIC |
Yes |
FLOAT |
DOUBLE PRECISION |
Yes |
REAL |
REAL |
Yes. The precision of SQL Server is 7 digits, while that of GaussDB is 6 digits. If the REAL value of the source database has 7 digits, 1-digit precision loss will occur when the value is synchronized to the destination database. |
SMALLMONEY |
NUMERIC(10,4) |
Yes |
MONEY |
NUMERIC(19,4) |
Yes |
BIT |
BOOLEAN |
Yes |
DATE |
DATE |
Yes |
SMALLDATETIME |
SMALLDATETIME |
Yes |
DATETIME |
TIMESTAMP WITHOUT TIME ZONE |
Yes |
DATETIME2 |
TIMESTAMP WITHOUT TIME ZONE |
Yes |
DATETIMEOFFSET |
TIMESTAMP WITH TIME ZONE |
Yes |
TIME(p) |
TIME(P) WITHOUT TIME ZONE |
The value can be accurate to seconds. Decimals are discarded. |
TIMESTAMP |
BYTEA |
Yes |
XML |
CLOB |
Yes |
CHAR |
CHARACTER |
Yes. If a column of this type in the source database contains characters that occupy more than one byte, increase the length of the column in the destination database. |
VARCHAR |
CHARACTER VARYING() |
Supported |
VARCHAR(max) |
CLOB |
Supported |
NCHAR |
CHARACTER VARYING() |
Supported |
NVARCHAR |
NVARCHAR2 |
Yes. If a column of this type in the source database contains characters that occupy more than one byte, increase the length of the column in the destination database. |
NVARCHAR(max) |
CLOB |
Yes |
BINARY |
BYTEA |
Yes |
VARBINARY |
BYTEA |
Yes |
VARBINARY(max) |
BLOB |
Yes |
IMAGE |
BLOB |
Yes |
HIERARCHYID |
BYTEA |
Yes |
NTEXT |
CLOB |
Yes |
TEXT |
CLOB |
Yes |
UNIQUEIDENTIFIER |
CHARACTER(36) |
Yes |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot