People seem to care about deadlocks
That’s why I wrote sp_BlitzLock. Why not sp_BlitzDeadlock?
Well, I had this song stuck in my head. But enough about that.
While poking around with things recently, I created a pretty typical deadlock on a table, but this one had a clustered column store index on it.
Of course, that makes things different.
objectivity
So we go digging
The deadlocks I generated were on a single object. Just a couple inserts and deletes in two separate transactions. Nothing special.
This is the information that I pull out with sp_BlitzLock
Hey Mister DJ
But what’s missing from the column store deadlock information is really weird. Namely, everything.
Oooookay
One may be tempted to try to use the associated object id to get the object name, and one would be left wanting.
SELECT OBJECT_NAME(72057594059948032) Msg 8115, Level 16, State 2, Line 12 Arithmetic overflow error converting expression to data type int.
I wish you would.
And so, dear reader
I am currently unable to give you as much information about column store deadlocks as I’d like to.
Unless Microsoft responds to my Connect Feedback Item.
Brent says: this is such a great example of why niche features run into interoperability issues. They work just fine by themselves, but they’re not tested in combination with other things – even when those things might be mainstream, like deadlock graphs. I bet this bug gets fixed quickly though – with columnstore indexes gaining popularity, more folks will be running into this issue fast.
Save $300 on our new SQL ConstantCare® today with coupon code MoveFaster. Saturday, it drops to $250...