I'm running into a problem with a table in two copies of a database I work with.

One copy which is online, has a clustered index, which when we run sp_MSIndexSpace on the table, has the clustered index at 801,568 KB. This is a backup from the 2nd database done a week ago.

The second copy of the database, which is the one production updates daily, has the same clustered index for the table at 5,414,344 KB, for a smaller set of records.

The indexes are created by a script which is run once a week, on the production database.

Is anyone aware of any tools or ways to find out why or how this index jumped 700% in a week when we ended up with approximately 100,000 records less. (The production table has 62,359,869 records while the web table has 62,455,014 records.)

Thank to all

Michael Schnell
[email protected]