Below is a small sample (top 20ish) from over 8000 indexes in avg_fragmentation_in_percent descending order. Will this cause any performance issues?
Sql-server – Is high index fragmentation an issue on performance
fragmentationindexsql server
Related Question
- Sql-server – SQL Server Index, difference between Average fragmentation and Total fragmentation
- Sql-server – 100% index fragmentation
- Sql-server – Index with high fragmentation percentage
- Sql-server – Factors to consider while Rebuild/Reorganize of index in SQL Server 2012
- Sql-server – Index Fragmentation – log issues
Best Answer
I would start by quoting from Old Books Online for SQL Server 2000 version. Microsoft Books Online (The SQL Server 2000 BOL is now removed by MS so the link is not present. Although its for SQL Server 2000 but gives very accurate definition )
Plus and fact being that since index is small pages are most likely to be in memory so no physical I/O would be required to get page and hence fragmentation would not come in picture.
So the small indexes which have
page_count <1500
or for that sake < 3000 is hardly going to cause any performance issue, it is quite likely that pages would be in memory and physical I/O would not be required hence fragmentation would actually not matter. If I look at your output only two indexes withpage_count 66K+
should really cause some performance issue if SQL Server has to scan index pages. People can argue that page_count of 5000 could also be deciding factor and to which I would say "not really", considering the definition from old books online quoted above. You must also note that the fragmentation we are talking is logical fragmentation where leaf level page order does not matches that of clustered index key.So performance issue, if any, could only come from large fragmented index not the smaller ones.