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 |
|
amsqlguy
Yak Posting Veteran
89 Posts |
 Posted - 2008-07-18 : 15:06:09
|
| guys,I have quick question - our environment is a low volume OLTP environment with upto 400 rows updated/inserted/deleted in 40 tables every day.In this environment would it be prudent to run the a job update index statistics on every table each week. Currently I update index statistics only whenI refresh the database with data (which is I trucnate all the data and run ETL program to load all the tables from source data).Any suggestions and inputs would be helpfulThanks |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-07-18 : 15:30:15
|
| I'm not sure if it would be prudent, but you might as well schedule it to run for performance reasons. How big (or small) is your database?Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
 |
|
|
amsqlguy
Yak Posting Veteran
89 Posts |
Posted - 2008-07-18 : 16:19:17
|
| I have 4gb database.I guess I am trying to find out what is an ideal scenario that would require index statistics update. For me when there is data refresh (purging all the data and reloading the data) I would require index.Any suggestions/inputs would helpThanks |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-19 : 00:56:30
|
| For 4gb db, rebuild all indexes may only take couple minutes. |
|
|
|
|
|
|
update index statistics