Re: How to control developers writting better SQL

This is a very interesting discussion and the problems are ones that I have experienced in my career. For the bulk of my career, I have been a developer, with most of that time spent before the internet was what it is today. I was developing client/server decision support applications. This was back in the day where the only optimizer was the rule based optimizer. It was even worse back then. We had to worry about very specific things such as the relative sizes of the tables and what order to place tables in the from clause etc... The development team was constantly under fire due to poor sql performance. My knowledge of sql was and is pretty big and I was able to work with a very cooperative dba at the time to learn all of the various specifics of writing efficient sql. In the end what we ended up doing was modularizing the application level code putting all sql generation functionality into a single module which I and only I (with some help from the dba) was allowed to maintain. We used a source control system as well. Although it did take quite a bit of time to rearchitect the application to work with this module, the long term benefits of it were amazing.

The oracle optimizer has changed much since then, but the habits, best practices and lessons I've picked up from that experience, I still use today, though I've had to assume more of a dba role these days because we don't have one and I'm the closest thing to one. But I won't call myself a dba just yet.

Gavin

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Thu Oct 26 2000 - 16:17:24 CDT