Abstract
As explained in Chapter 8, rowstore index column values are stored in the leaf pages of an index’s B-tree structure. Columnstore indexes are also stored in pages, but not within a B-tree structure. When you create an index (clustered or nonclustered) on a table, the cost of data retrieval is reduced by properly ordering the leaf pages of the index and the rows within the leaf pages, whereas a columnstore has the data pivoted into columns and then compressed, again with the intent of assisting in data retrieval. In an OLTP database, data changes continually, causing fragmentation of the indexes. As a result, the number of reads required to return the same number of rows increases over time. A similar situation occurs with the columnstore as data is moved from the deltastore to the segmented storage areas. Both these situations can lead to performance degradation.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2018 Grant Fritchey
About this chapter
Cite this chapter
Fritchey, G. (2018). Index Fragmentation. In: SQL Server 2017 Query Performance Tuning. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-3888-2_14
Download citation
DOI: https://doi.org/10.1007/978-1-4842-3888-2_14
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-3887-5
Online ISBN: 978-1-4842-3888-2
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)