Fix tempdb collation conflicts with DATABASE_DEFAULT, compare a join-level COLLATE, and inspect contained-database behavior.
Snapshot Isolation Update Conflicts: Handling Error 3960
Reproduce snapshot isolation update conflict error 3960, compare read committed snapshot, and retry the whole transaction safely.
Connection Pooling Problems: Timeouts, Leaks and Max Pool Size
Diagnose connection pooling timeouts with session counts, sleeping activity, open transactions, and client settings that divide pools.
SQL SERVER – Fix : Error: 257 Implicit conversion from data type datetime to int is not allowed.
Implicit conversion from data type datetime to int is not allowed. I hit this error with ISNULL and a date, and the fix is right in the message: use CONVERT.
Cannot Resolve the Collation Conflict (Msg 468): SQL in Sixty Seconds #047
Cannot resolve the collation conflict is Msg 468, and it appears when two text columns use different collations. I reproduced it on SQL Server 2025 with a temp table, found the mismatched columns with a query and tested three fixes, from a COLLATE clause in the query to changing the column itself.
SQL SERVER – Fix – Error: 1060 The number of rows provided for a TOP or FETCH clauses row count parameter must be an integer
Error 1060 says the rows for a TOP or FETCH clause must be an integer. I tracked down its cause in a friend’s 10000 line stored procedure and fixed it.
Finding Procedures Created With the Wrong SET Options
Find procedures with wrong SET options in sys.sql_modules, understand error 1934, and recreate modules with ANSI_NULLS and QUOTED_IDENTIFIER ON.