Sysindexes table showing unexpected indid entries?

[dimbulbz]

A simple query of the sysindexes table is returning up to 220 indid entries for a table that only has one index/key defined. what causes the additonal entries? most tables only have one entry per defined index. The entries also show zero pages associated with them. Does this indicate some kind of problem with the table?

Jim Johnston
dimbulbz@hotmail.com

 

[hmckillop]

By default, SQL Server creates statistics for columns in a table if an index doesn't already exist for the column. The query optimizer then evaluates the statistical information about the distributions of data ranges within the column to choose a more efficient query-processing plan. Distinguishing an automatically-created statistic from a real index is easy. In SQL Server 7.0 and SQL Server 2000, an auto-created statistic starts with the prefix _WA_Sys.

You can also determine whether an index is real or an auto-created statistic by using the IsAutoStatistics property of the INDEXPROPERTY() function. Let the SQL Server optimizer select which statistics to create. You can also keep the auto_create_statistics option enabled for databases that you manage



"I'm living so far beyond my income that we may almost be said to be living apart