Gosh... another great article, Solomon. As with anything else, planning and having the resources available for parallel table existance is important but this article covers a problem that a whole lot of people have had even on just SSC. Instead of explaining the whole gambit in the future, I'm just going to point them to this article if they have the extra disk space. Very well done.
As a side bar, I agree with you about triggers in general but especially on the type of triggers needed to pull off this bit SQL prestidigitation. If they are well written and supported by correct indexing, they don't add much in the line of overhead at all.
Again, my hat's off to you for this great article.
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