It is a phenomenon only on table with clustered index.
When if happens, SQL Server tries to use 50/50 policy,which means half of data remains on old page and half of data goes to newly allocated page.
Non-clustered indexes won't be impacted by page split in version later than 7.0 because they use KEY insgead of RID to locate record.
the reason it can have page split is because table with clustered index is an index and its entries are stored as their sorting orders.
No comments:
Post a Comment