December 30, 2009 at 10:13 am
I have a SQL database I recently migrated from SQL 2000 to SQL 2005. In SQL 2000 I disable auto-update statics and ran a weekly scheduled job to update the statics on the SQL Server. After moving the Database I re-enabled auto-update statics and create statistics and still keep a scheduled job that would do a full statistics update weekly. I have one table that has roughly 15k records and can be updated every 5 minutes. On AVG there is about 400 updates daily. After about 3 days with about 8% change the statics become so out of wack that the processor pegs to 100% till I update manually update statics. Do I just assume that this is normal behavior and schedule a job to run nightly or every few hours just to update that one table or should I be looking elsewhere.
Any advice would be helpful.
Thank you
December 30, 2009 at 11:02 am
Did you follow MS's recommendations on upgrading from 2000 to 2005, including updating useage?
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply