• Does this table have a clustered index? If not, you might see this behavior. I am not 100% sure but I have seen this happen in SQL 2000 but I have never come across this situation in SQL 2005 DB.

    -Roy