Improve company productivity with a Business Account.Sign Up

x
?
Solved

SSIS 2005 - How to identify the colum causing the error in OLEDb Destination component

Posted on 2011-03-12
6
Medium Priority
?
1,131 Views
Last Modified: 2012-05-11
Can anyone tell me how to identify the specific column name that is causing an error when attempting to insert a data flow into an OLEDB Destination component?  I am attempting to create a lot which specifies the error that occurred and the field name that caused the error.  I am able to get the column ID, but I don't know how to translate this into a meaningful column name.  Example:  I get an "error field" value of 6581.  I don't know which field is represented by 6581, so I don't know what column is causing the problem.  I checked the sys.columns and sys.all_columns views to see if the column_id referenced by SSIS was perhaps one of those values, but I could not find anything useful there.

Below is a sample of code that is our best attempt at the moment to figure this out, but it seems really ugly.  I'm using a script task and hard-coding to convert the error column id into an error column name.

I'm sure there is a better way to do this with no hard-coding.

P


Public Overrides Sub Input0_ProcessInputRow(ByVal Row As Input0Buffer)
        '
        ' Add your code here
        '

        Row.ErrorDescription = ComponentMetaData.GetErrorDescription(Row.ErrorCode)
        If Row.ErrorColumn = 6581 Then
            Row.ErrorColumnName = "SUBMISSION_ID"
        Else
            Row.ErrorColumnName = Row.ErrorColumn.ToString()

        End If
    End Sub

End Class

Open in new window

0
Comment
Question by:jbaird123
  • 4
  • 2
6 Comments
 

Author Comment

by:jbaird123
ID: 35123459
dbaSQL:  Thanks for the information, but this does not quite answer my question.  The first article explains how to get the error description - which I am already doing.  The second article appears to be showing how to extract the data from all fields in the data flow, but it does not show how to identify which column caused the error.

There is an ErrorColumn field which identifies the column that caused the error, but the value in this field is something cryptic like "6851".  I don't know how to figure out which field in the data flow is represented by "6851".  

Can you explain how to figure this out?  It seems like there should be an easy solution for something like this.  

Thanks.
0
 
LVL 17

Accepted Solution

by:
dbaSQL earned 2000 total points
ID: 35123620
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
LVL 17

Assisted Solution

by:dbaSQL
dbaSQL earned 2000 total points
ID: 35123630
Also looks like these guys did the same thing you're trying to do:
http://www.sqlservercentral.com/Forums/Topic456102-148-1.aspx
0
 

Author Closing Comment

by:jbaird123
ID: 35159053
Thank you. The code at http://eod.codeplex.com/ is very helpful for implementing these solutions.
0
 
LVL 17

Expert Comment

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

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

by Mark Wills PIVOT is a great facility and solves many an EAV (Entity - Attribute - Value) type transformation where we need the information held as data within a column to become columns in their own right. Now, in some cases that is relatively…
by Mark Wills Attending one of Rob Farley's seminars the other day, I heard the phrase "The Accidental DBA" and fell in love with it. It got me thinking about the plight of the newcomer to SQL Server...  So if you are the accidental DBA, or, simp…
SQL Database Recovery Software repairs the MDF & NDF Files, corrupted due to hardware related issues or software related errors. Provides preview of recovered database objects and allows saving in either MSSQL, CSV, HTML or XLS format. Ensures recov…
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.

601 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