I've approached this type of situation , assuming I am deleting from the target table thouasnds of records that still would not make up a majority of the rows, using...

I found Erland Sommarskog's articles on SQL Error Handling very helpful. They are very detailed, and very long, but gave me a lot of reassurance that I understood all...

Thank you for the nice article and breaking things down for us. Yes the mathematics of how much % gain is a interesting one. As I like to see it...

• This reply was modified 4 years, 12 months ago by MMartin1.

Being a leader start with being you and not trying to be someone else. This comes down to confidence, Confidence is contagious in a good way. A good leader will...

Getting  back to your orignal article, thank you Gail for providing a feasible and simple alternative to the "get it done now" culture. Your article highlights the importance of caring...

@MMartin1 - Most of the flamers selectively read the article(s).  In this case, they don't understand that you were demonstrating best practices of defense against worst practices of database...

Its not about my design as much as what someone might encounter. Not...

• This reply was modified 5 years, 2 months ago by MMartin1.

Thank you for the fine article. Where does the concept of indek "seek" and index "scan" fit into this article? It would be good to cover if not already planned...

READUNCOMMITTED and NOLOCK cannot be specified for tables modified by insert, update, or delete operations. The SQL Server query optimizer ignores the READUNCOMMITTED and...

But...

The...

Thank you for the article. The NOT IN operation > I would steer clear of this for performance and the potential for it to blow up if there is an...

• This reply was modified 6 years, 8 months ago by MMartin1. Reason: less wording

I know about the hesitation with open transactions, but hard to be too careful when it comes to ensuring the data manipulation is done correctly.

You can use something like the below to indicate a total failure somewhere. At least in the testing phase.

begin transaction 

declare @rowcount int
Select @rowcount = count(*) from...

I can imagine :). I get those as well on posts I did a long time ago. Surprise.!