July 18, 2002 at 10:58 am
Our application has a procedure that calls several other procedures within a TRANSACTION block. The problem is that sometimes the calling procedure will quit without finishing (i.e. will execute procedures 1&2 but not 3&4) and roll everything back that was executed.
I ran a trace and recreated the problem. The strange part is that it records the BEGIN TRANSACTION, the execution of the successful called procedures but there is no ROLLBACK or error messges. It just records the successful operations and then goes on to the next operation after the TRANSACTION block.
Does Profiler (SQL 7.0) record any rollback information if a BEGIN TRANSACTION/COMMIT TRANSACTION block fails? I included everything in the trace.
If not is there some other way to troubleshoot this situation? I tried some error recording within the transaction but, of course, it gets rolled back too. Thanks for any help anyone can offer.
Edited by - kmeehan on 07/18/2002 10:59:06 AM
July 18, 2002 at 11:27 am
How about just turning off the transaction while you debug? I always add them last so I dont have to fight them while working through the design/initial testing.
Andy
July 18, 2002 at 12:17 pm
quote:
How about just turning off the transaction while you debug? I always add them last so I dont have to fight them while working through the design/initial testing.Andy
http://www.sqlservercentral.com/columnists/awarren/
July 18, 2002 at 6:01 pm
I'd follow Andy's suggestion for troubleshooting. Be sure you don't have a commit inside any of hte procedures or it may be committing without you expecting it.
Steve Jones
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply