(function() { var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(ga); })();
Home > SQL > Time bomb coding

Time bomb coding

February 11th, 2010 Leave a comment Go to comments

I come accross a great artical by David Poole on SQLServercentral about Time Bomb Coding

Well worth the read

At some point in your career you will be asked to get involved in diagnosing performance problems with a database application. Sometimes the diagnosis is simple but in other cases the causes of poor performance are subtle. From my own experience I have noticed that subtle performance bugbears conform to a pattern and I refer to this pattern as “Time Bomb Coding”. The pattern I am referring to has the following properties

  • The system is well established
  • There has been no significant alterations to the system for some considerable time
  • Statistics and indexes are kept up-to-date
  • Execution plans appear reasonable at first glance
  • The database design appears to be simple and clean
  • Traffic has not changed much over time

Despite this the system performance has been steadily degrading!

If this seems familiar to you then you are probably a victim of time bomb coding. In this article I should like to give a few of the many examples of this phenomenon I have come across.


Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • LinkedIn
  • Slashdot
Categories: SQL Tags: , ,
  1. No comments yet.
  1. No trackbacks yet.

Powered by WP Hashcash