Just spent a business day prototyping a partition-switch mechanism to improve the performance of a weekly data feed of 50M rows into a 12,000,000,000 row table. It takes ten hours. Most of this time is rebuilding the indexes, which they disable before the load. The process duration of the new mechanism is under ten minutes, two minutes of which is rebuilding the indexes in the switch table.
"Do you want some help implementing this?" "No thanks. It happens on Saturdays. We'll get around to it."
The existing process has failed for the last four Saturdays, io timeouts.
I'll get me coat.
Chris, that sounds like it could be very interesting. Are you going to write an article on it?
Ed, you know very well I prefer walking around the office naked to writing articles! It's very well documented online already. I'm not sure I'd have anything of note to add. Except perhaps, having everything in one place.
Like around 20% of the IT workforce here I'll be redundant at the end of next month. Lack of time won't be an excuse then.
[font="Arial"]Low-hanging fruit picker and defender of the moggies[/font]For better assistance in answering your questions, please read this[/url].
Understanding and using APPLY, (I)[/url] and
(II)[/url]
Paul White[/url]
Hidden RBAR: Triangular Joins[/url] / The "Numbers" or "Tally" Table: What it is and how it replaces a loop[/url] Jeff Moden[/url]