July 9, 2008 06:57am pdt

1. chapmandew 1,545,836
2. angelIII 1,231,150
3. aneeshat... 517,561
4. mark_wills 415,981
5. ee_rlee 348,824
6. ScottPle... 287,651
7. dtodd 272,301
8. acperkins 190,773
9. Thomasian 151,038
10. cs97jjm3 135,235
11. matthews... 131,903
12. EugeneZ 128,009
13. ptjcb 119,637
14. appari 113,498
15. dbaSQL 112,669

1. angelIII 10,187,563
2. aneeshat... 4,575,440
3. acperkins 4,179,233
4. ScottPle... 4,101,703
5. arbert 2,245,195
6. Lowfatsp... 2,165,176
7. chapmandew 1,545,836
8. rafrancisco 1,460,132
9. imran_fast 1,458,588
10. EugeneZ 1,404,171
11. Hilaire 1,221,775
12. Nightman 1,143,404
13. Mr_Peerapol 1,087,815
14. nmcdermaid 1,060,022
15. ptjcb 1,053,496

04.06.2006 at 08:41AM PDT, ID: 21804213

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.4

Cannot convert between unicode and non-unicode string data types (SSIS 2005)

Zone: MS SQL Server

Tags: unicode, convert, between, cannot, string

I have an Excel Source component hooked to an OLE DB Destination component in my SSIS 2005 Data Flow Task. After I mapped the excel columns to the OLE DB table columns i get these errors below. I noticed that for the first error, the Excel Field format (when you mouse over the column name in the mappings section in OLE DB component) is of type [DTWSTR] and the corresponding SQL field from my SQL table that it's mapping to is of type [DT_STR] when mousing over that field in the mappings in the properties of my OLE DB component. All table fields in SQL Server for the table I'm inserting into are of type varchar

TITLE: Package Validation Error
------------------------------

Package Validation Error

------------------------------
ADDITIONAL INFORMATION:

Error at Data Flow Task [OLE DB Destination [27]]: Columns "Commission Agency" and "CommissionAgency" cannot convert between unicode and non-unicode string data types.

Error at Data Flow Task [OLE DB Destination [27]]: Column "Product" cannot convert between unicode and non-unicode string data types.

Error at Data Flow Task [OLE DB Destination [27]]: Columns "Officer Code" and "OfficerCode" cannot convert between unicode and non-unicode string data types.

Error at Data Flow Task [OLE DB Destination [27]]: Columns "Agency Name" and "AgencyName" cannot convert between unicode and non-unicode string data types.

Error at Data Flow Task [OLE DB Destination [27]]: Columns "Agency Id" and "AgencyID" cannot convert between unicode and non-unicode string data types.

Error at Data Flow Task [OLE DB Destination [27]]: Columns "Tran Code" and "TranCode" cannot convert between unicode and non-unicode string data types.

Error at Data Flow Task [OLE DB Destination [27]]: Columns "User Id" and "UserID" cannot convert between unicode and non-unicode string data types.

Error at Data Flow Task [OLE DB Destination [27]]: Columns "Acct Number" and "AccountNumber" cannot convert between unicode and non-unicode string data types.

Error at Data Flow Task [DTS.Pipeline]: "component "OLE DB Destination" (27)" failed validation and returned validation status "VS_ISBROKEN".

Error at Data Flow Task [DTS.Pipeline]: One or more component failed validation.

Error at Data Flow Task: There were errors during task validation.

(Microsoft.DataTransformationServices.VsIntegration)

Start your free trial to view this solution

Question Stats

Zone: Microsoft

Question Asked By: dba123

Solution Provided By: Sirees

Participating Experts: 2

Solution Grade: A

Translate:

Loading Advertisement...