Lock Timeouts & Memory (Dear SQL DBA Episode 37)
The dev server got bogged down during a deployment and lock timeouts were everywhere. Was the perfmon counter way off about how much memory was being used just for locks?
The dev server got bogged down during a deployment and lock timeouts were everywhere. Was the perfmon counter way off about how much memory was being used just for locks?
Trace Flag 4199 has been in SQL Server for a while. I’ve long thought of this as the “Bucket of Optimizer Hotfixes” trace flag: enabling it turns on a variety of hotfixes that have been implemented over the years.
As I’ve gotten back into the swing of a more-or-less regular work schedule after the initial launch of SQL Workbooks, I’ve revived some of my favorite work habits and free tools.
![]()
I’m a big fan of the time-tracking tool Toggl. Β Their tools are easy to use, and even the free version is very cool.
Tracking time may seem like a giant pain if you’re used to using terrible tools for it. But Toggl is simple, and it helps keep me sane.
A little while back I wrote about Why Indexes Reduce Locks for Update and Delete Queries.
I got a great question on the post from Zac:
Whatβs not super clear is why it takes out a lock on the whole table, is this because it does a lock escalation as a result of the Full Scan? Will this always happen, or is there a threshold of record update counts where this will occur?
This was tough to answer in just a comment, so I promised a full post on the topic.
A database transaction log is expanding, even though the DBA is running log backups and doesn’t see an open transaction? What’s going on with this Availability Group?
I recently got an interesting question from a reader about running a CREATE INDEX statement with DROP_EXISTING
I’ve started up a weekly newsletter! Sign up, and each Tuesday you’ll get a link to a quick SQL Server quiz or poll in your inbox. Most weeks there will be a cartoon thrown in there, too.
Copyright (c) 2025, Catalyze SQL, LLC; all rights reserved. Opinions expressed on this site are solely those of Kendra Little of Catalyze SQL, LLC. Content policy: Short excerpts of blog posts (3 sentences) may be republished, but longer excerpts and artwork cannot be shared without explicit permission.