These commands specify different reservepagegap values for the table and the clustered index, and a value for the nonclustered type_price index:
sp_chgattribute titles, "reservepagegap", 16
create clustered index title_ix on titles(title) with reservepagegap = 20
create index type_price on titles(type, price) with reservepagegap = 24
Table 9-9 shows the effects of this sequence of commands.
Command |
Allpages-locked table |
Data-only-locked table |
---|---|---|
create clustered index or clustered index rebuild due to reorg rebuild |
Data and index pages: 20 |
Data pages: 16 Index pages: 20 |
Nonclustered index rebuilds |
Index pages: 24 |
Index pages: 24 |
For allpages-locked tables, the reservepagegap specified with create clustered index applies to both data and index pages. For data-only-locked tables, the reservepagegap specified with create clustered index applies only to the index pages. If there is a stored reservepagegap value for the table, that value is applied to the data pages.