SQL Server limits, done the way a record book does them. Not what the documentation says, but what happened when I tried one more. Eleven records, each attempted on SQL Server 2025 build 17.0.4085.5, each with the exact error text at the edge. One documented figure turned out to be wrong on this…
SQL Server Triggers on Trial: The State Versus the Trigger
SQL Server triggers, tried in open court. The prosecution says they’re slow, hidden and wrong. The defence says they’re the only witness in the room. Four exhibits were measured on SQL Server 2025, and the judge rules at the end.
Case-Insensitive Unique Constraints in a Case-Sensitive Database
Enforce case-insensitive unique user names in a case-sensitive database using an indexed computed column with an explicit collation.
Checking Constraints After a Bulk Load With DBCC CHECKCONSTRAINTS
Run DBCC CHECKCONSTRAINTS after a controlled bulk-load bypass, inspect violations, and restore enabled trusted CHECK and foreign-key rules.
NOCHECK CONSTRAINT: Loading Data and Trusting Foreign Keys Again
Use NOCHECK CONSTRAINT carefully, distinguish enabled from trusted foreign keys, validate old rows, and restore optimizer assumptions.
A Unique Constraint That Allows Many NULLs
Allow many NULLs while enforcing unique non-NULL values with a filtered SQL Server index, required SET options, and tested queries.
Self-Referencing Foreign Keys: Managers, Employees and Deletes
Delete a manager and SQL Server says no, which is good. See how to reassign reports safely and how to catch loops the foreign key allows.