Home Dashboard Directory Help
Search

Found unknown column type conversion by Christoph Muthmann


Status: 

Closed
 as Fixed Help for as Fixed


8
0
Sign in
to vote
Type: Bug
ID: 771818
Opened: 11/21/2012 4:06:55 AM
Access Restriction: Public
3
Workaround(s)
view
4
User(s) can reproduce this bug

Description

I'm using SQL Server 2012 SP1 Client.
When I try in SSMS the task "Export Data" with a query, not the table itself and the table has colunns of type varchar, an error occurs.
Error is e. g.:
Found 2 unknown column type conversion(s)
You are only allowed to save the package

The version of the sql server database does not matter. The client makes the difference.
Details
Sign in to post a comment.
Posted by Microsoft on 6/17/2013 at 10:50 AM
Item moved to archive.
Posted by P'tite Poupoune Verreault on 4/25/2013 at 10:11 PM
well actually there is some server that you have to check to be sure your are installaling the right version for your systeme , you have to carefull
Posted by Microsoft on 4/25/2013 at 11:16 AM
Hello Christoph. Thanks for bringing this to our attention. This problem has been fixed. The correction will be included in a future release for SQL Server. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by Microsoft on 4/25/2013 at 11:16 AM
Hello Christoph. Thanks for bringing this to our attention. This problem has been fixed. The correction will be included in a future release for SQL Server. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by JayKirkman on 3/29/2013 at 8:28 AM
Has there been any solution to this since it was reported on 20 FEB 13? I also have been having the problem, and have been unable to obtain a satisfactory solution. Thanks!
Posted by Microsoft on 2/20/2013 at 2:16 PM
Hello Christoph. Thank you for bringing this to our attention. We really do appreciate the feedback. We’ll investigate and get back to you.

Appreciated,
-Walter A Jokiel
Program Manager, SQL Server
Posted by Bjorn D. Jensen on 1/17/2013 at 1:06 AM
In some cases you can export the base tables instead,
but if they are big, this is not a real workaround.
Sign in to post a workaround.
Posted by AndyCnZh on 7/10/2014 at 1:01 AM
I add some type definition in the MSSQLToSSIS10.XML, then I can import the data successfully.


    1. Open file MSSQLToSSIS10.XML
    
    C:\Program Files (x86)\Microsoft SQL Server\110\DTS\MappingFiles\MSSQLToSSIS10.XML
    
    2. Add these lines
    
    <!-- 202 -->
    <dtm:DataTypeMapping >
        <dtm:SourceDataType>
            <dtm:DataTypeName>202</dtm:DataTypeName>
        </dtm:SourceDataType>
        <dtm:DestinationDataType>
            <dtm:CharacterStringType>
                <dtm:DataTypeName>DT_WSTR</dtm:DataTypeName>
                <dtm:UseSourceLength/>
            </dtm:CharacterStringType>
        </dtm:DestinationDataType>
    </dtm:DataTypeMapping>    

    <!-- 203 (max) -->
    <dtm:DataTypeMapping >
        <dtm:SourceDataType>
            <dtm:DataTypeName>203</dtm:DataTypeName>
        </dtm:SourceDataType>
        <dtm:DestinationDataType>
            <dtm:SimpleType>
                <dtm:DataTypeName>DT_NTEXT</dtm:DataTypeName>
            </dtm:SimpleType>
        </dtm:DestinationDataType>
    </dtm:DataTypeMapping>    
    
    3. Restart the MSSQLServer services(if you don't success, please do this step).

        4. Re-import data.
Posted by Microsoft on 5/3/2013 at 2:56 PM
Another workaround is to use the ".NET Framework Data Provider for SqlServer" instead of the "SQL Server Native Client 11.0".

-Charles Gagnon (chgagnon@microsoft.com)
Posted by JayKirkman on 3/29/2013 at 8:32 AM
I get this error when attempting to export data through the SQL import/export wizard. One workaround that has been suggested is create SSRS packages, but for quick ad-hoc data jobs that seems cumbersome. My workaround has been to create a View on the server with the code for the data I want to export, then export that View rather than the raw query itself. Although it represents extra steps, it does sidestep this problem and exports fine.