October 18, 2010 at 7:45 am
Hi all,
Recently, we're experiencing performance problems with sql server 2000.
We have created a job that updates statistics for some tables every night. The problem is that this job seems to have no effects in database performance even if the running status is always succeeded.
When there is a performance problem, running the job manually it makes not any difference (also the running status is succeeded), but running the update statistics commands manually (from query analyzer) the performance problem disappears.
Do you have any idea what may be wrong with that job?
October 18, 2010 at 8:08 am
There's probably nothing wrong with the job. Not all performance problems go away with a stats update. You may well have a combination of poor indexing and poorly written queries.
Check if the job is doing sampled or fullscan updates. Are you doing sampled or fullscan updates manually? Are you running the job against the right database? Is it succeeding?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 18, 2010 at 12:25 pm
GilaMonster thank you about your reply...
The job is doing sampled updates (the default behavior) as well as the manual update and of course i am running the job against the right database.
I don't know if there is a combination of poor indexing / queries. The weird here is the different behavior of sql server (job vs. query analyzer) ....
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply