pablavo (3/24/2010)
I should have added that the main table will be truncated before every import and the new data added to it. So you suggest that it's a good idea to rebuild after importing the data to the main table. Does your question ask me why I want to rebuild after every import? I don't know if I do, that's why I set up the thread... Since the table is truncated every 30 minutes and new data added, will the indexes have to be rebuilt or would the table be fine since it's truncated?
If you're talking about a non-clustered index, I think I would drop the index after truncating the table, then import the new data, then re-create the index. It would speed up the import (possibly considerably, depending on the index), and the index would be rebuilt as efficiently as SQL was able to.
If it is a clustered index, keep the index in place during import, but see if you can order the incoming data in the same order as the clustered index would order it, so you'll be filling pages in sequence.
Rob Schripsema
Propack, Inc.