Eirikur Eiriksson (5/28/2015)
Brandie Tarvin (5/28/2015)
Well, unless someone used DBCC Timewarp() on it, the last I checked there was only one. But then again, someone did say DBCC Timewarp() was outdated and being downgraded. I don't remember what it was supposed to be replaced with, but maybe that new function / proc / whatever managed to duplicate another crystal ball for us.And then someone ran off with it without mentioning that there was a new one...
The crystal ball has a shared memory connection directly to the core of the DBCC Timewarp, this fools the optimizer into doing a reverse and forward time parallel scan within the notorious time sort operator, hence it can appear in many places at the same time.
😎
Well, that explains why I was seeing some of the things I saw in my execution plan this morning. The proximity to the crystal ball was linked to DBCC Timewarp. It's becoming clearer now.