Showing Error While Mapping NVARCHAR Column

[Debasis.Sharma]

Showing Error While Mapping NVARCHAR Column.

[Gadi.Farhat]

What is the error? What are you doing exactly?

[Debasis.Sharma]

Created a TEST table on Source DB with following
[T1] [int] NOTNULL,
[T2] [nchar](10)NULL,
[T3] [nvarchar](50)NULL,
[T4] [nvarchar](max)NULL,
[T5] [decimal](18, 10)NULL,
[T6] [varchar](max)NULL,
[T7] [varbinary](max)NULL,

T1 Primary Key

Created Same TEST table on Destination DB

Try Attunity CDC it's not working

TITLE: Package Validation Error
------------------------------
Package Validation Error
------------------------------
ADDITIONAL INFORMATION:
Error at Full Load Data Flow [TEST Full Load Destination [34]]: Column "T2" cannot convert between unicode and non-unicode string data types.
Error at Full Load Data Flow [TEST Full Load Destination [34]]: Column "T3" cannot convert between unicode and non-unicode string data types.
Error at Full Load Data Flow [SSIS.Pipeline]: "component "TEST Full Load Destination" (34)" failed validation and returned validation status "VS_ISBROKEN".
Error at Full Load Data Flow [SSIS.Pipeline]: One or more component failed validation.
Error at Full Load Data Flow: There were errors during task validation.
(Microsoft.DataTransformationServices.VsIntegratio n)
------------------------------
BUTTONS:
OK
------------------------------

[Gadi.Farhat]

Hi,

The error you are getting is because the Full Load Source component exposes Unicode columns (nvarchar) as string (DT_STR) and the Full Load Destination component which uses the SQL Server Native OLEDB provider exposes unicode columns as Unicode (DT_WSTR).


Use one of the following options to solve this problem:

1. Add a Covert transformation between the Full Load Source and the Full Load Destination components to convert the columns from DT_STR to DT_WSTR.

2. Add a new OLEDB Connection Manager to the package that uses the SQL Server Native OLEDB provider to connect to the source database and, replce the Connection Manager used by the Source component with the new created Connection Manager.


Regards,

Gadi