Post reply

Trap LOCK_TIMEOUT but suppress error

  • October 6, 2009 at 7:31 am

    #156290

    Is there a way to catch @@ERROR = 1222 but to suppress the fact that it has happened so call routines don't know that the stored procedure call has errored.

    Please note that I'm using SQL 2000

  • October 6, 2009 at 7:54 am

    #1062254

    This is an interesting request. Can you explain a bit further? Does the action that is failing not actually need to happen? If so, why is it occurring in the first place? What kind of constraints are you under as far as re-working the sp or your architecture?

    Also, there is a 2000 forum here for future reference(Don't copy this post over there), and a lot of us read both.

    http://qa.sqlservercentral.com/Forums/Forum8-1.aspx

    Seth Phelabaum

    Consistency is only a virtue if you're not a screwup. 😉

    Links: How to Post Sample Data[/url] :: Running Totals[/url] :: Tally Table[/url] :: Cross Tabs/Pivots[/url] :: String Concatenation[/url]

  • October 6, 2009 at 8:17 am

    #1062270

    Ooops I'm so used to posting into this forum I forgot that I was having a problem with 2000 :blush:

    The issue is that I am updating a table and if I can't lock the record then I want to ignore this transaction and move onto the next. The problem is the the SP is being called via Execute SQL task in SSIS and when the error occurs it branches down the error route rather than continuing on. Only when I get locked records do I want to suppress this so SSIS doesn't know an error of this magnitude has occurred.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply