• patrickmcginnis59 (12/12/2012)


    I'm always on the lookout for surprises like this, having just recently learned that Microsoft still cannot fundamentally manage storage (http://support.microsoft.com/kb/307487 "can't resize tempdb while in use" also known as failing comp sci 101), I'm sort of trying to collect info traps like this and that.

    The surprise(or should it be ??) is that it is a bug, as acknowledged by them more than a year ago. I dont see this as being completely addressed with SP2, and was curious to see if anyone else had run into something like this. We have virtualized all the environments that I had benchmarked this on since this occurred last, and I am not about to go change our production environment to test this out. When the proverbial s**t hit the fan last year, the workaround was to limit the DOP on all queries (by setting MAXDOP in sp_configure) and take it out of the optimizer's hands so we dont run into this again. Who knows how much overhead we are now incurring because it would actually be optimal to parallelize a query !! I would not like to second guess the optimizer if given a choice, but in this instance, we didn't have a choice. I've posted this on MSDN forums too with the case number, and MS techs generally patrol those forums, so I am hoping for something concrete from them.