Wednesday, September 17, 2008 | byAmith Nagarajan
Most organizations work on performance tuning in depth during an initial software implementation. After a go-live, however, it is fairly common to see performance tuning fall off the radar. The issue with this is that the database and related components are constantly evolving and require review on a recurring basis. We recommend to our clients to conduct a performance tuning review at least quarterly during the first year of use of our product and at least semi-annually thereafter. Some organizations can get away with less frequent performance tuning efforts and some need to evaluate their environment more often. The key thing to remember is that you have to build a plan to review performance on a recurring basis to make sure that system performance stays steady, or preferably improves. If you don’t, it is likely that performance will slowly degrade over time as the performance tuning that was done earlier is no longer optimal.
This is a key issue for all of your enterprise database software applications. The good news is that the incremental tuning exercises are typically not very time consuming once you establish a baseline. We recommend that people put this on their calendar along with other scheduled reviews such as a recurring security review and disaster recovery plan review.