OT Discussion- Priority of Performance Tuning...
Date: Wed, 26 Oct 2011 10:16:42 -0700 (PDT)
I am about to approve this comment out on my blog from one of my favorite DBA God's: "Yep, like Cary is saying " 90% of performance tuning is politics". I am paraphrasing. Don't hold me to the exact quote or percentage.I don't understand "priorities for the business may not be the same as a priority for the DBA’s". If it is not a priority for the business why should it be a priority for the DBA? Politics work both ways. You are skating close to CTD. If nobody else cares about performance why should you?" I respect his opinion and it did get me thinking about where performance tuning falls in the priority of tasks for most database environments. I commonly am brought into places that have a history of bringing code/designs to production in a short time-span, business requirements and/or revenue demanding that everything works being more important than it working efficiently or performing well, then my job is to go in and correct this "little oversight".
I honestly don't think it's intentional by the business to move poor performing or code that will only be able to sustain the business for a short period of time into production, it's just due to the demands of the business for many companies. This does, however, make performance tuning a lesser priority in many environments, (and keeps me in demand and well employed... :))
As I specialize in this area, I now question the kind DBA's on the list to see if you also find performance tuning a lesser priority in the environments you've worked in. I'm also curious what kind of environment it is, (private sector, retail, banking, government, etc..) Just like disaster recovery and other tasks that DBA's may put a higher priority on, the business, as it does not always directly correspond to revenue, does not view as part of the goal...
Please feel free to email me directly if you wish to remain anonymous..
Sr. Database Administrator and Developer DBAKevlar.com