Comments on: Avoiding the ‘WHERE clause wasn’t selected’ problem https://lobsterpot.com.au/blog/2020/05/14/avoiding-the-where-clause-wasnt-selected-problem/ Thu, 14 May 2020 10:34:02 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Rob Farley https://lobsterpot.com.au/blog/2020/05/14/avoiding-the-where-clause-wasnt-selected-problem/#comment-3661 Thu, 14 May 2020 10:34:02 +0000 http://blogs.lobsterpot.com.au/?p=3978#comment-3661 Right, but then you end up holding the locks for longer. And if someone runs it and walks away, it can be disastrous.

]]> By: Victor Girling https://lobsterpot.com.au/blog/2020/05/14/avoiding-the-where-clause-wasnt-selected-problem/#comment-3660 Thu, 14 May 2020 10:12:33 +0000 http://blogs.lobsterpot.com.au/?p=3978#comment-3660 An alternative is to use a transaction

BEGIN TRAN

UPDATE …

— Number of rows looks ok?
— COMMIT TRAN
— Oops
— ROLLBACK

]]> By: Rob Farley https://lobsterpot.com.au/blog/2020/05/14/avoiding-the-where-clause-wasnt-selected-problem/#comment-3659 Thu, 14 May 2020 02:27:30 +0000 http://blogs.lobsterpot.com.au/?p=3978#comment-3659 Yes, there are a number of tools that will warn about that. But often I have to give scripts to other people to run, and I generally can’t get them to install those tools.

]]> By: John Berry https://lobsterpot.com.au/blog/2020/05/14/avoiding-the-where-clause-wasnt-selected-problem/#comment-3658 Thu, 14 May 2020 02:24:49 +0000 http://blogs.lobsterpot.com.au/?p=3978#comment-3658 Hate when that happens! I think every SQL dev or DBA has made this mistake at least once. An alternative protection mechanism is the Devart SQL Complete execution warnings feature.

]]>