May 3, 2012 at 7:13 am
is it advisable to stop the update statistics job while its still running on prod env...its taking longer to complete (more than 3 hrs)
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
May 3, 2012 at 9:30 am
Sapen (5/3/2012)
is it advisable to stop the update statistics job while its still running on prod env...its taking longer to complete (more than 3 hrs)
I think update statistics can be stopped. It should not cause any issue.
3 hrs is too much. Check whether it is blocked. Check what is the status of that job. What exactly it is doing.
May 3, 2012 at 9:37 am
No it was not blocked... it took around 3.5 hours to complete.
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
May 3, 2012 at 1:59 pm
Sapen (5/3/2012)
is it advisable to stop the update statistics job while its still running on prod env...its taking longer to complete (more than 3 hrs)
Update stats can be killed mid stream and any work done to that point on completed tables will be kept, but progress generating stats for the table being worked on at the moment the process was stopped will be lost.
3.5 hours is a long time. What do you mean by "the update stats job"? Is it running sp_updatestats? Maintenance plan? How big is the DB? Did you run WITH FULLSCAN?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
May 3, 2012 at 3:28 pm
Its a maintenance plan with full scan....I am running this on all the user databases and the biggest of them are
250GB and 80GB rest of them are like less than 1 GB
Thanks.
“If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply