DTS Wizard 2008 R2 ServicePack2+CU3 not work with some data types - by Aruba.it

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 773549 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 12/5/2012 7:57:24 AM
Access Restriction Public


After installing CU3 for SQLServer 2008 R2 SP2 the Import export wizard fails with the following error while importing-exporting data from a SQL database, selecting "Query" as data source, 
[Source Information]
Source Location : xxxx
Source Provider : SQLNCLI10
Table: [Query]
Column: VarcharField
Column Type: 200
SSIS Type: (Type unknown ...)
Mapping file (to SSIS type): C:\Program Files (x86)\Microsoft SQL Server\100\DTS\MappingFiles\MSSQLToSSIS10.XML

The unknown data types are:


How to reproduce the bug:

1. Create table using the script below
Use [TEST]
CREATE TABLE [dbo].[TestExport](
 [VarcharField] [varchar](100) NULL,
 [NvarcharField] [nvarchar](100) NULL,
 [TextField] [text] NULL,
 [NtextField] [ntext] NULL,
 [VarBinaryField] [varbinary](50) NULL,
 [XmlField] [xml] NULL,
 [ImageField] [image] NULL
2. Right – click on Database TEST and select Tasks -> Export Data
3. On Data Source page select the SNAC 10 (the same behaviour is with the Microsoft OLEDB provider for SQL Server)and database TEST
4. On Destination page select SNAC 10 (the same behaviour is with the Microsoft OLEDB provider for SQL Server) and new/existent database
5. On Specify Table Copy or Query page select Write a Query to Specify the Data to Transfer and then write the query below and click Next and then Next again
Select * from Testexport
6. On reviewing Data Mapping page you will see the error:
 Found 7 unknown column type conversion(s)
 You are only allowed to save the package
7. If you select Copy data from one or more tables or view on the step 5 the data is exported without any issue.
8. The issue is NOT reproduced with the .NET Framework Data provider for SQL Server. 

Additional informations:
- The file C:\Program Files (x86)\Microsoft SQL Server\100\DTS\MappingFiles\MSSQLToSSIS10.XML is correct and contains the nodes for said data types;
- the problem is in the client, not in sql server engine: if i try the same export from the same database, using another client version, it works fine.
Sign in to post a comment.
Posted by Marc K 4096 on 4/24/2014 at 7:24 AM
This has been fixed in Cumulative update package 12 (CU12) for SQL Server 2008 R2 Service Pack 2 (http://support.microsoft.com/kb/2938478)
Posted by Marc K 4096 on 10/29/2013 at 6:46 AM
Mainstream support is still active for SQL Server 2008 R2. Please also fix in this edition. Upgrading to SQL Server 2012 or 2014 is not possible for some at this time.
Posted by Microsoft on 7/25/2013 at 9:27 AM
Hello Aruba. Thanks for bringing this to our attention. We are aware of this problem, and it has been addressed in SQL 2012 SP2 & SQL 2014.

-Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)