The rowcount for table properties in Enterprise Manager is obtained from the sysindexes system table. The reason they do that is that using "select count(*)..." results in a table scan or an index scan and can take very long time to execute on large tables. SQL Server does a pretty good job in keeping the rowcount column up to date but the rowcount is not guaranteed to be always accurate. It looks like you hit one those times where the field is not up to date. Try running the sp_updatestats in that database, very often it takes care of the issue. In my experience, about one in twenty tables is a few rows off.

Roman


>I'm looking at the properties of a table and it says it has 0 records even though when I go to view all rows it has a bunch of records. Has anybody encountered this? is this some type of corruption?
>
>Thanks