Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cidr
Posting Yak Master
207 Posts |
 Posted - 2010-03-10 : 13:51:22
|
| Hi there,Wasn't sure to put this thread here or on Reporting servevices.I'm developing a financial report and each night a job will run to pull data from a number of different dbs and tables into one reporting table. This table will first be truncated before this process. Each night there will obviously be more rows than the last, taking account for the previous days transactions I'd like to know if it's a good idea to drop the indexes when the table is truncated, then when the data is added, to rebuild the indexes, ready for the next days reporting.Also, if this is a good idea, should I use a higher fill factor for the indexes?Many thanks |
|
|
dinakar
Master Smack Fu Yak Hacker
2507 Posts |
Posted - 2010-03-11 : 00:50:58
|
| Thats an option worth trying. It depends on how fast your box is. Indexing can take a while sometimes. So, note down the current time it takes for the data feed, then try the other option of dropping the indexes, disable any constraints, insert data, rebuild indexes. Since the data seems to be used only for reporting i.e read only, use all the space in the index - 100% fillfactor.Dinakar Nethi************************Life is short. Enjoy it.************************http://weblogs.sqlteam.com/dinakar/ |
 |
|
|
cidr
Posting Yak Master
207 Posts |
Posted - 2010-03-24 : 06:35:11
|
| Hi Dinakar,Sorry for not getting back to you sooner! thanks for your advice with thisPaul |
|
|
|
|
|
|
|
|
Rebuilding indexes on a table