May 11, 2011 at 10:18 am
just wondering if there is any reason not to update statistics on msdb and master databases?
thanks
May 12, 2011 at 12:07 am
The reson which I can think of is:
1. Data in the master/msdb do not change frequently.
2. Objects do not grow much.
3. There are no heavy insert/update/delete.
4. Referenced & used by other databases/jobs etc.
HTH
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
May 12, 2011 at 2:41 am
Ideally, the statistics need to be updated or are updated :
1. When you do alot of DMLs in your tables or indexed views.
2. If the schema changes happen on your objects.
3. Index are rebuilded.
But in real scenario such things don't happen with system databases much .
Regards,
Sachin
May 17, 2011 at 11:12 am
sachnam (5/12/2011)
Ideally, the statistics need to be updated or are updated :1. When you do alot of DMLs in your tables or indexed views.
2. If the schema changes happen on your objects.
3. Index are rebuilded.
But in real scenario such things don't happen with system databases much .
Regards,
Sachin
On the other hand, the overhead, expense, and elapsed time for updating the statistics in those databases is small.
Just to handle all contingencies, why not update the statistics in those databases? I doubt that your system or users will notice it.
Use the following SQL code to selectively update the statistics in those databases:
USE Master
EXEC sp_UpdateStats
USE msdb
EXEC sp_UpdateStats
LC
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply