March 17, 2009 at 12:23 am
Comments posted to this topic are about the item SSIS Custom Error Handling
Cheers
http://twitter.com/widba
http://widba.blogspot.com/
March 18, 2009 at 7:41 am
I would like to give this a try. However, I've never added a custom component and I'm struggling with registering it. I'm using Visual Studio 2005. I'm not finding a gacutil.exe that I obviously need so I can register it. Any help is appreciated. Thanks!
March 18, 2009 at 7:48 am
The article references using 2008 - follow the link to Jack's original article, he has the components setup for 2005.
Cheers
http://twitter.com/widba
http://widba.blogspot.com/
May 3, 2009 at 11:59 am
First, I really want to thank you for this component. It really made my life lots of easier.
But somehow, I SSIS_LOG_ERROR table, all the ErrorDesc contains "No status is available. ". When I know the error id caused by FK constrain.
Do I miss anything?
Any help is greatly appreciated.
February 24, 2010 at 8:44 am
It seems like anytime there is an error with the entire row, such as a PK constraint, you get that same message. I have tried a couple of other scripts and they return the same information.
I have a question about the field name column. Within my table I get '<fields />' with a hyperlink to an xml file. The only thing in this file is the same <fields /> text. Any ideas why I wouldn't be getting the field name or is there a trick to getting it?
Thanks in advance.
February 24, 2010 at 9:36 am
I figured it out. I forgot to check the individual columns that I wanted to see in the buffer.
February 24, 2010 at 10:09 am
sorry - had the message 1/2 typed out and got pulled away. you need to select the columns you want persisted into the XML- as you said
I need to open the code up and see why the error messages are generic. I focused more on the data gathering than the actual error, but that was the narrow focus that I was going after.
Cheers
http://twitter.com/widba
http://widba.blogspot.com/
April 22, 2010 at 12:51 pm
I have registered the component successfully to add to the BIDS Toolbox, however, I do not see the custom component listed. I am using Visual Studio 2005 with SQL Server 2005.
C:\Documents and Settings\1\My Documents\SSISLogging\bin>reg.cmd
C:\Documents and Settings\1\My Documents\SSISLogging\bin>copy "C:\Documents and
Settings\1\My Documents\SSISLogging\bin\SSIS.Logging.dll" "C:\Program Files\Micr
osoft SQL Server\90\DTS\PipelineComponents\"
1 file(s) copied.
C:\Documents and Settings\1\My Documents\SSISLogging\bin>"C:\Program Files\Micro
soft Visual Studio 8\SDK\v2.0\Bin\sn.exe" -Vr "C:\Program Files\Microsoft SQL Se
rver\90\DTS\PipelineComponents\SSIS.Logging.dll"
Microsoft (R) .NET Framework Strong Name Utility Version 2.0.50727.42
Copyright (c) Microsoft Corporation. All rights reserved.
Verification entry added for assembly 'SSIS.Logging,55BF2292469930A5'
C:\Documents and Settings\1\My Documents\SSISLogging\bin>"C:\Program Files\Micro
soft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" /if "C:\Program Files\Microsoft S
QL Server\90\DTS\PipelineComponents\SSIS.Logging.dll"
Microsoft (R) .NET Global Assembly Cache Utility. Version 2.0.50727.42
Copyright (c) Microsoft Corporation. All rights reserved.
Assembly successfully added to the cache
April 22, 2010 at 12:57 pm
Jack Corbett's article (mine is a derivative of his) talks about SQL/VS 2005 implementation. This article refers to a 2008 version - sorry.
Cheers
http://twitter.com/widba
http://widba.blogspot.com/
April 22, 2010 at 1:01 pm
Yes, I was able to successfuly implement Jack's version, however, I really wanted to add the script to the toolbox, for ease of developement.
So, this version will only work in 2008?
April 22, 2010 at 1:28 pm
I only tested it in 2008 -> I can't say that it doesn't work since I jumped over the 2005 versions.
Cheers
http://twitter.com/widba
http://widba.blogspot.com/
May 4, 2010 at 11:55 am
I have come up with a query to dynamically crosstab your xml fields, I posted it on Jack's discussion, the link is below. Thanks
http://www.sqlservercentral.com/Forums/Topic487637-1254-11.aspx
July 14, 2010 at 7:20 am
This is good stuff. Thanks a ton for sharing this.
February 7, 2012 at 10:56 am
I have done Error Handling by getting the Error Column name from the lineageId and forming custom error message.
http://www.nkannan.com/2012/02/error-handling-in-ssis-dft.html
Thanks,
Nk
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy