I recently encountered an issue where an index rebuild set to wait_at_low_priority ended up blocking an asynchronous statistics update.
This interaction led to a large blocking chain where queries were waiting on the async stats update and started to timeout.
In SQL Server, using the KILL command to terminate a session results in an entry being logged in the error log.
This raises the question: Does the ALTER INDEX REBUILD command with the WAIT_AT_LOW_PRIORITY option also log its actions in the error log?
Read a cautionary tale on how I’ve deceived the SSMS, then promptly forgot about it and, in turn, ultimately confused myself.
Here are the chronicles of my struggles to add a large Clustered index to a View without causing an outage.
Have you ever encountered a situation where you mark the constraint as trusted, but the next day, it’s back to untrusted again? This blog post will help you find the cause.
I’m reminding myself how to set up secure CrossDB access. This blog post includes a nifty diagram and follow-along example.
How can 15 be less than 13? Let’s have a look at this unexpected, but fully documented behaviour.
