Heh... I beg to differ, Steve. You did NOT compromise. You simply made it easier for someone else to do the work and, as it turns out, may have saved your own back in the process. You "enabled" someone else!
And THAT's the secret to success... "LET them see it YOUR way". In order to do that, you sometimes have to help them along. As David Poole once noted, the extraordinary DBA is the one you seek out first, not use as a last resort.
By the way, you once suggested that throwing hardware at performance problems was the way to go... why don't you take a ride to the local tractor store and buy one of those hand-crank, wheeled tounge posts and make it so easy for the Mrs. that she'll actually thank you for making it easier to do a "crap job"?
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