Solved

How to convert between uni-code and non-unicode string data types

Posted on 2011-03-23
4
1,816 Views
Last Modified: 2012-05-11
I am trying to upload from excel spreadsheet two columns in text format, to a table in sql 2008 data type varchar

column names from excel to sql table are the same

code
description

Trying to upload SSIS Package Excel Source 2010 to OLE DB destination

Error messages on two columns

Error at Data Flow Task [OLE DB Desintation [151[]]: Column "Code" cannot convert between unicode and non-unicode string data types.

Error at Data Flow Task [OLE DB Destination [151]]: Columns "Description"  cannot convert between unicode and non uni-code string data types.


I have tried different string types but nothing is working. what should I format the spreadsheet two, numbers, text or general

0
Comment
Question by:Amanda Walshaw
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 17

Accepted Solution

by:
dbaSQL earned 500 total points
ID: 35204570
0
 

Author Comment

by:Amanda Walshaw
ID: 35204753
thanks for that followed those instructiosn but on my ole destination getting the following error

SSIS package "Package.dtsx" starting.
Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Data Flow Task 1, SSIS.Pipeline: Validation phase is beginning.
Warning: 0x802092A7 at Data Flow Task 1, OLE DB Destination [202]: Truncation may occur due to inserting data from data flow column "Code2" with a length of 50 to database column "Code" with a length of 2.
Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Warning: 0x80049304 at Data Flow Task, SSIS.Pipeline: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available.  To resolve, run this package as an administrator, or on the system's console.
Warning: 0x80047076 at Data Flow Task, SSIS.Pipeline: The output column "Hierarchy 3 Code" (43) on output "Excel Source Output" (22) and component "Excel Source" (14) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
Warning: 0x80047076 at Data Flow Task, SSIS.Pipeline: The output column "Hierachy 3 Description" (46) on output "Excel Source Output" (22) and component "Excel Source" (14) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
Information: 0x40043006 at Data Flow Task, SSIS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Data Flow Task, SSIS.Pipeline: Pre-Execute phase is beginning.
Error: 0xC0202009 at Data Flow Task, Excel Source [14]: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E37.
Error: 0xC02020E8 at Data Flow Task, Excel Source [14]: Opening a rowset for "Suggested$" failed. Check that the object exists in the database.
Error: 0xC004701A at Data Flow Task, SSIS.Pipeline: component "Excel Source" (14) failed the pre-execute phase and returned error code 0xC02020E8.
Information: 0x4004300B at Data Flow Task, SSIS.Pipeline: "component "PINVREP08" (137)" wrote 0 rows.
Information: 0x40043009 at Data Flow Task, SSIS.Pipeline: Cleanup phase is beginning.
Task failed: Data Flow Task
Warning: 0x80019002 at Package: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution method succeeded, but the number of errors raised (3) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "Package.dtsx" finished: Failure.
0
 

Author Closing Comment

by:Amanda Walshaw
ID: 35204815
worked it out had to back through the entire ssis package put togehter
0
 
LVL 17

Expert Comment

by:dbaSQL
ID: 35206249
Glad you got it worked out.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

     When we have to pass multiple rows of data to SQL Server, the developers either have to send one row at a time or come up with other workarounds to meet requirements like using XML to pass data, which is complex and tedious to use. There is a …
Naughty Me. While I was changing the database name from DB1 to DB_PROD1 (yep it's not real database name ^v^), I changed the database name and notified my application fellows that I did it. They turn on the application, and everything is working. A …
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question