Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations sizbut on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ssis package problem

Status
Not open for further replies.
Jun 9, 1999
45
HK
I have created a package which export a table in SQL2k5 to a dbase file. I created a SQL native client and a MS Jet 4.0 OLE Jet DB provide. I make Source point to SQL native client connection manager and OLE DB destination point to MS Jet 4.0 OLE Jet DB provide connection manager in Data Flow specification. When I try to run the package, it saids all the columns cannot between unicode and non-unicode string data types. Is there any setting I need to change. Please help. Thanks.
 
Hi,

In Visual Studio, under ToolBox - Data Flow Transformations, add a DAta Conversion item in between the Source and Destination items.

You can then convert each column to another datatype.
Then, in the destination, see Mappings, in there you can choose the input fields (original - unchanged or copy of original but with changed datatype).

Hope this helps.

Regards

TK
 
Sorry. I don't quite get you. How can I solve the unicode problem again?

 
I solved the problem by adding data conversion task between source and
destination. But this does only for append. How can I do it for overwrite?
Thanks.
 
Your best bet is to delete the file first then export into it. You can use a .NET Script object to delete the file.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top