SSIS Error : Cannot Convert between unicode and non-unicode string datatypes

SSIS Error : Column '%s' Cannot Convert between unicode and non-unicode string datatypes.

We will get this error when the destination Table column datatype is Nvarchar and  OutPut Column Data Type  in SSIS Transformation  is String[DT_STR] then you will get this error .


We can solve this error by giving Correct datatype in this case ie  Unicode String [DT_WSTR]

you can set the value as shown in below fig .







Comments

Post a Comment

Popular posts from this blog

SSAS : A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient). + Solution

Problem : have installed Analysis service on my server machine through remote login from my service account. I am able to open Analysis services from there. When I open SSMS from the same service account on my local machine, I am not able to connect to that Analysis service. It is giving me error by saying : "A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running. (Microsoft.AnalysisServices.AdomdClient). A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connection host has failed to respond 10.245.192.111:2382(System)." Solution : Based on my research, the issue was caused by the Browser Service account was changed to the domain account. In your scenario, you can try to connect to the Analysis Service using <Servername>:2383 instead of instance name. Or you can change the Browser Service account to "Local System"....
Read more

SSIS Error : Unable to infer the XSD from the XML file. The XML contains multiple namespaces

Image
Problem : When we have Multiple Namespaces in the Xml Source which we need to load the Data from   as we shown below Then we will face a issue in generating XSD for that XML Error : Unable to infer the XSD from the XML file. The XML contains multiple namespaces. (Microsoft Visual Studio) Solution : First we need to avoid multiple namespaces to transform your source file to a format that doesn’t refer to the namespaces. SSIS has an XML task that can do the transformation. 1) Add the XML task to an SSIS   Control Flow and edit it. 2) Change the OperationType property value to XSLT, the SourceType to File connection and the Source to your source file that has the problem. 3) Set the SaveOperationResult property to True and expand the OperationResult branch. Set DestinationType to File Connection and the Destination to a new XML file ( ModifiedInput.XML). 4) Add the below script to a new file and save it with an xslt file extension (Input.XSL...
Read more

SSRS : [Teradata Database] 3939 There is a mismatch between the number of parameters specified and the number of parameters required.

Error : [Teradata Database] 3939   There is a mismatch between the number of parameters specified and the number of parameters required. When we get this Error : when we are creating SSRS reports on Teradata database and in which when we are using parameters in the dataset in wrong style\format. Just for Info :  to connect Terdata we need to have  .Net Data provider for Terdata  when we installed this on our machine  Then we are able to see Teradata data source type in SSRS. How to Solve this issue :  This error will come if we are not using correct syntax to create parameterized data set .  The correct way is we need to ?  for parameter The report parameters can be named or unnamed. Teradata only supports unnamed parameters. An unnamed parameter is denoted by a ‘?’, and is merely a placeholder for data that is going to be entered at report processing time. For example, the following is a dataset with a single-value ...
Read more