Recently I was studying for the MCM exam and one of the things that came up in my research was the idea of temporary indexes. I had never used them before and was intrigued by the idea. I have dropped indexes before a large load and then recreated them, but these are indexes I planned to keep on the table indefinitely.
There are always processes that you run periodically on some schedule. These might be end of month, or end of year processes where you run a series of reports or queries that aren't necessarily run at other times in your business cycle.
Since this was a new concept for me, I wanted to ask and see how many others might actually be using this. Maybe you'll get an idea for how to speed up some of the periodic, but very important, processes you run. For this Friday:
Do you use temporary indexes?
By temporary, I mean indexes that you create for a process and then discard at the end of a process. These could be indexes that you use to supplement some type of data load, perhaps indexes used in staging tables. Or they could be indexes that are added to some OLTP tables for the processing of certain reports in a short period of time.
However you might implement them, let us know how you use them, and how they have improved performance for you.
The Voice of the DBA Podcasts
The podcast feeds are available at sqlservercentral.mevio.com. You can also follow Steve Jones on Twitter:
Today's podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.
I really appreciate and value feedback on the podcasts. Let us know what you like, don't like, or even send in ideas for the show. If you'd like to comment, post something here. The boss will be sure to read it.