Yikes. Thanks for pointing that out Jeff.
I've only (reluctantly) used it with very small sets, mostly in pre-2K5 code.
I'll be checking my code now...
You bet and thanks for the feedback.
If you have something big, a properly configured "Quirky Update" is both bullet-proof and lightning quick. It'll process a million rows in less than 3 seconds on most machines. There are some pretty strict rules to follow to make sure it doesn't go "quirky" on you, but it's usually worth it. It even beats the new functionality they added to SUM() OVER in 2012. It is, however, unsupported and if that's a problem for someone, then just use a recursive CTE or even a fire-hose cursor (likely better than the rCTE but haven't tested it) to do the running total.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs