SQL Server Import and Export Wizard Does Not Recognise Varchar and NVarchar - by Julie Koesmarno

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


75
0
Sign in
to vote
ID 775897 Comments
Status Closed Workarounds
Type Bug Repros 25
Opened 1/5/2013 11:01:52 PM
Access Restriction Public

Description

When importing data retrieved via a query using the SQL Server Import and Export Wizard in SQL Server 2012, the VARCHAR Type is recognized as "200" while NVARCHAR Type as "202". This cause the wizard to show "Review Data Type" warning/error that looks similar to the following:
Found 14 unknown column type conversion(s)
You are only allowed to save the package

This means that the data transfer cannot be executed and the wizard will only be able to save the transfer as an SSIS package.

The issue seem to only appear if the data source is a query - i.e the "Write a query to specify the data to transfer" in the Specify Table Copy or Query section of the SQL Server Import and Export Wizard.

Choosing "Copy data from one or more tables or views" option in the Specify Table Copy or Query section seems to recognize the VARCHAR and NVARCHAR data type properly.
Sign in to post a comment.
Posted by MarvelMayfield on 8/14/2014 at 1:07 PM
FYI... just experienced this issue on SQL Server Ent. 2012 SP1 CU9. The databases used for export/import are the same Collation type, so that can be ruled out: SQL_Latin1_General_CP1_CI_AS. Fortunately, creating a view from the select query was a quick & easy workaround.
Posted by billrosspaxedi on 8/14/2014 at 7:57 AM
The problem seems to relate to accessing data that came from a different collation/code page.
Posted by Keith Spitz on 6/18/2014 at 9:40 AM
This may be a duplicate of the link (see comments below), but that connect bug is marked as "closed/fixed" even though the bug is still present after applying SQL Server 2012 Cumulative Update 9. I'm voting/commenting here as well.
Posted by AlsaceZhang on 5/13/2014 at 4:15 AM
MS is really suck
Posted by Microsoft on 1/25/2013 at 3:35 PM
Thanks you for your input. This is a duplicate of https://connect.microsoft.com/SQLServer/feedback/details/772761/dtswizard-in-sql-2012-sp1-no-longer-recognizes-nvarchar-varchar-data-types-when-source-is-a-query. Please vote on that connect bug if this is still an issue for you.
Posted by Julie Koesmarno on 1/5/2013 at 11:24 PM
It looks like a similar issue has been submitted here: https://connect.microsoft.com/SQLServer/feedback/details/772761/dtswizard-in-sql-2012-sp1-no-longer-recognizes-nvarchar-varchar-data-types-when-source-is-a-query#details

Please vote from the above link. This issue can be closed as it's a duplicate one.

Thank you,
Julie