NOLOCK double counting is how three people in a lunch line turn into four lunches. Nothing was inserted. One row moved ahead of the scan and got read twice. I tested it on SQL Server 2025 and share a query that catches it on your own table.
NOLOCK Can Miss Rows: The Order That Was Never Missing
Yes, NOLOCK can miss rows. A row can vanish from your report while it sits safely in the table. Nobody deleted it. The read simply walked past it.
UPDATE Without WHERE Clause: The Day Everyone Got a Raise
An UPDATE without WHERE clause changed 8,432 salaries. When ROLLBACK can help, and how to check the affected row count before COMMIT.
BULK INSERT Batch Size and ROWS_PER_BATCH
Distinguish ROWS_PER_BATCH estimates from BULK INSERT commit batches, then review logging, locks, rejected rows, and atomic loading.
SQL SERVER – Setting Deadlock Priority to Control the Transaction that is Rolled Back
In this article, we will explore Setting Deadlock Priority to Control the Rolled Back Transaction. Let us explore more in this blog post.
Implicit Transactions in SQL Server: The Setting That Leaves Work Open
Implicit transactions make SQL Server open a transaction on the first data statement and keep it open until a COMMIT or ROLLBACK. This post shows what starts one, how @@TRANCOUNT counts it, why a second session waits, and how to find and clear the sessions that left work open.
Data Quality Asserts in T-SQL: Failing a Load When Rules Break
Write data quality asserts in T-SQL to reject invalid staging rows, preserve check results, and record each load attempt.