david.holley (8/30/2012)
So basically a single transaction and then check @@Error after each statement as in...BEGIN TRAN
UPDATE
IF @@ERROR <> 0 GOTO ERR_HANDLER
DELETE
IF @@ERROR <> 0 GOTO ERR_HANDLER
DESTROY WORLD
IF @@ERROR <> 0 GOTO ERR_HANDLER
INSERT
IF @@ERROR <> 0 GOTO ERR_HANDLER
COMMIT TRAN
RETURN 0
ERR_HANDLER:
KILL KENNY
ROLLBACK
RETURN 1
That is not the best way to handle this. You should use try/catch instead the older style of constantly checking @@error.
BEGIN TRAN
begin try
UPDATE
DELETE
DESTROY WORLD
INSERT
COMMIT TRAN
RETURN 0
end try
begin catch
KILL KENNY
ROLLBACK
RETURN 1
end catch
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/