• john.wb - Thursday, May 18, 2017 6:44 AM

    Another good practice is to wrap any data affecting statements in a transaction but comment out the COMMIT TRAN. You can see how many rows are affected and issue a rollback if the number looks wrong.

    Not sure I agree that this is a good practice.  
    This was the "good practice" at a previous place I worked.  This caused a significant number of deadlocks while the users looked over the results of the query before doing the commit.

    Michael L John
    If you assassinate a DBA, would you pull a trigger?
    To properly post on a forum:
    http://www.sqlservercentral.com/articles/61537/