I once inadvertently coded an update script that looked something like this:
SET @User = 1234;
SET Status = 0
WHERE User = User;
From that point forward, I add a block of code that basically performs an assertion and then does a rollback + error if the actual number of rows affected falls outside an expected threshold.
UPDATE ... ;
IF @@ROWCOUNT > 10000
ERRORAISE ... ;
One nice to have T-SQL extension would be a way of declaring a rollback assertion within the DML statement itself, perhaps as a hint. If it would also leverage statistics to simply shortcut the DML operation without even starting it, then that would be even better.
UPDATE ... OPTION ( ASSERT MAX_ROWS_AFFECTED(10000) );
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho