http://sqlblog.com/blogs/linchi_shea/archive/tags/Logical+scan+fragmentation/Fragmentation/default.aspxTags: Logical scan fragmentation, FragmentationenCommunityServer 2.1 SP2 (Build: 61129.1)http://sqlblog.com/blogs/linchi_shea/archive/2009/06/22/performance-impact-logical-scan-fragmentation-100-may-not-be-as-bad-as-85.aspxMon, 22 Jun 2009 16:02:00 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:14831Linchi Shea5http://sqlblog.com/blogs/linchi_shea/comments/14831.aspxhttp://sqlblog.com/blogs/linchi_shea/commentrss.aspx?PostID=14831In this previous post I asked whether 100% logical scan fragmentation is always worse than 85% local scan fragmentation for table/index scans. (To be precise, I was talking about a B-tree table, i.e. a table with a clustered index). The answer is no....(<a href="http://sqlblog.com/blogs/linchi_shea/archive/2009/06/22/performance-impact-logical-scan-fragmentation-100-may-not-be-as-bad-as-85.aspx">read more</a>)<img src="http://sqlblog.com/aggbug.aspx?PostID=14831" width="1" height="1">Disk I/OFragmentationLogical scan fragmentationPerformanceStorage