Query store queries losing forced plans

A common question I hear when discussing forcing of plans in query store is, “Why did a plan I previously forced quit using the forced plan?”.  In most cases this is related to having a database in an Always On Availability Group.  If the database IDs in the availability group differs across the servers, plan […]

Read More

Negative blocking session ids

On occasion while examining lock scenarios, I’ve seen a lead blocker with a negative session ID.  After looking in the documentation for the blocking_session_id, it explained why I am seeing this (taken directly from Microsoft’s sys.dm_exec_requests documentation): -2 = The blocking resource is owned by an orphaned distributed transaction. -3 = The blocking resource is […]

Read More