Database tuning can be an incredibly challenging task, particularly when working with large-scale data where even the most minor change can have a dramatic impact on performance.
In mid-sized and large companies, most SQL database tuning will be handled by a Database Administrator (DBA). But believe me, there are plenty of developers out there who have to perform DBA-like tasks. Further, in many of the companies I’ve seen that do have DBAs, they often struggle to work well with developers—the positions simply require different modes of problem solving, which can lead to disagreement among coworkers.
On top of that, corporate structure can also play a role. Say the DBA team is placed on the 10th floor with all of their databases, while the developers are on the 15th floor, or even in a different building under a completely separate reporting structure—it’s certainly hard to work together smoothly under these conditions.
In this article, I’d like to accomplish two things:
- Provide developers with some developer-side database tuning techniques.
- Explain how developers and DBAs can work together effectively.