We have a mid size table (150 GB) that has 3 indexes. The primary key is clustered on its identity column. The other 2 indexes are unique. None of the columns in any of the three indexes are ever modified. All fields in the table are fixed length. We are using 2005 Standard.
Since the cluster is on the table's identity column, no index column ever gets updated (so no deferred updates) and all fields are fixed length what the potential causes for the fragmentation on the clustered index?
I know Sybase can defer updates when updating with Join, but I see no documentation the SQL Server does this anymore.
