Results 1 to 3 of 3
  1. #1
    Join Date
    Feb 2004
    Posts
    492

    Unanswered: sysindexes don't match

    It seems my sysindexes table is inaccurate on a nonclustered index. In my case the rowcount (rows and rowcnt) do not match the actual rowcount of the table. The command UPDATE STATISTICS doesn't change the rows or rowcount, adding 'FULSLCAN' won't budge rowcount either.

    After I did a dbcc reindex, the number of rows matched, however, upon adding rows in the table both rows and rowcount are out of sync again.

    It's a fairly straightforward table, no triggers, no computed fields, only integer, datetime, varchar and bigint columns. There's a clustered index on a bigint column and a nonclustered index on a integer column.

    dbcc show_statistics show that the nonclustered index is updated and it's rows and rows sampled match the number of rows in the table (not in the sysindexes-table).

    I'd like to know if I'm chasing ghosts here or if there's something very wrong here. What could be causing the counts being inaccurate? Anyone who could shed some light?

  2. #2
    Join Date
    Aug 2002
    Location
    Prague
    Posts
    77
    hi, as far as i know columns in sysindexes are not guaranteed to hold precise values. See 'DBCC UPDATEUSAGE' topic in BOL. Mainly COUNT_ROWS clause. mojza

  3. #3
    Join Date
    Feb 2004
    Posts
    492
    ok, thanx mojza. Still think it's scary though.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •