August 22, 2002 at 6:59 am
anyone have any ideas why the 'used' value in sysindexes gets seriously out-of-whack for system-generated stats (those starting with '_WA...')? I have several denoting such values as 1,800,000,000 and so on for a table that is 1 or 2 pages. I have tried updating stats and so on, but the only thing that seems to fix the problem is to drop the stat. When SQL auto-creates it again later, it has valid values (i.e. 1 or 2 etc). Any thoughts?
Brian Glass
Sr. Database Adminstrator
Bombardier Aerospace
August 22, 2002 at 1:52 pm
Nope. Is this in general, or following a big delete/truncate? Do you update stats manually or set the db option? What SQL version?
Andy
August 22, 2002 at 3:03 pm
quote:
Nope. Is this in general, or following a big delete/truncate? Do you update stats manually or set the db option? What SQL version?Andy
http://www.sqlservercentral.com/columnists/awarren/
SQL 2000 SP2 with numerous post-SP2 security patches. This is under normal transactional activity. Have the auto-update and auto-create switches set. Manually trying to update them does no good either.
Consequently, this causes the taskpad tables view in SQL 2000 EM to give a 'no records found' message. I have written a script to clean it up (drops all system-generated statistics greater than 10000 used pages in a database).
Brian Glass
Sr. Database Adminstrator
Bombardier Aerospace
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply