No Significant Fragmentation? Look Closer

Posted by: Simple Talk, on 28 Feb 2012 | View original | Bookmarked: 0 time(s)

If you are relying on using 'best-practice' percentage-based thresholds when you are creating an index maintenance plan for a SQL Server that checks the fragmentation in your pages, you may miss occasional 'edge' conditions on larger tables that will cause severe degradation in performance. It is worth being aware of patterns of data access in particular tables when judging the best threshold figure to use....

Category: SQL | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 299 | Hits: 0

Similar Posts

  • Implementing a WCF service firewall part II of N more
  • Lexing and Parsing more
  • 'Oslo' SDK - January 2009 CTP more
  • Multi-Value Key for a Dictionary more
  • The Onion Architecture : part 2 more
  • Optimization Tips: Optimizing Custom Skins more
  • Visual Studio 2008 Plug Ins more
  • Who needs an architect anyway? Part II - The architect and architecutal decisions more
  • Dynamic Type Invokation in .NET more
  • Recent Patch hosing ASP Classic COM? more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD