RE: Options for poorly performing SQL

> -----Original Message-----
> From: Michael Fontana
>
>
> The root cause is that people who write application code appear to
have an
> unreasonable disdain for everything not in the programming language of
choice,
> of which SQL is notoriously not. The only way I've ever seen this
overcome is
> to have a database programming design and development group. Anyone
who
> designs a database application without rigorous attention to the
critical
> database interface to their application are simply not serious or
professional
> at all.
>
> --
> http://www.freelists.org/webpage/oracle-l
>

You make it sound as if that were true of all app people. I'm an 'app people'. Although, I have to admit that you have a point. I do see that attitude a lot. Since I could give a rodent's behind for any particular language or DB ( RDBMS or otherwise ), I use whatever is best suited to my app. When it comes to getting my data, I try to figure out how to best do that. Of course, I've practically become a DBA in the process.

Since I run Oracle on a Windows and a Linux box for sport ( AIX for production ), I had to learn and perform DBA duties. I see the effort that my DBAs go through to support my app. It's only fair that I do the same. And we constantly look for DB resource hogs. Sometimes adding more memory or disk space isn't going to make any difference.

--
http://www.freelists.org/webpage/oracle-l