Over the last few articles I have talked about SQL optimisation and how support teams can make a difference if they know how to optimise the SQL.
I gave an overview of the SQL Tuning areas that I think support teams should know about. In my last article I talked about the business impact of poor queries.
Support teams are often under resourced and it can be difficult to persuade people to invest in SQL optimisation training.
Talking to managers about technical terms, like explain plans, indexes and SQL Warning log messages, may not convince them to invest in the training.
Consider taking a different approach – think about the impact of SQL related problems.
At a next coffee break do a little research/thinking:
- How many “poor performance” meetings have you/your team been in and how much did that cost?
- How much additional value could have been delivered if the support staff were not investigating performance problems/meetings?
- How many users have suffered delays because of the poor performance?
- How much did the delays cost ?
- How much more efficient could the users be if the system was quicker?
- How many slow SQL warnings are being logged?
You may be surprised by the cost of existing performance problems.