... applied to the parent who spoiled the child ...
Jerry Whittle
ASIFICS DBA
NCI Information Systems Inc.
[EMAIL PROTECTED]
618-622-4145
-----Original Message-----
From: Kevin Lange [SMTP:[EMAIL PROTECTED]
...� large burlap sack and a small bat ....
-----Original Message-----
From: Loughmiller, Greg [mailto:[EMAIL PROTECTED]]
duct tape
-----Original Message-----
From: Tim Gorman [mailto:[EMAIL PROTECTED]]
Sybase, Schmybase, Oracle, Schmoracle -- the concepts are still the same.� Developers create tables and indexes and then write SQL, thinking that the RDBMS is at fault if performance doesn't match expectations.
�
They have to understand that the structures they have created or the queries they have written may simply be inefficient, expending too much work.� I don't know how to measure that in Sybase, but I'm reasonably sure that there must be a way.
�
I used to joke that I could get Oracle�ERP/Apps�to run on a Palm Pilot if I were permitted to really�tune the SQL.� The work performed by an application is not an immutable monolith, especially with the Oracle RDBMS and all of the performance statistics it keeps.� It is very much susceptible to improvement.
�
First, they must make a reasonable attempt to *fix* the problem (by making SQL more efficient).� If that doesn't work, then�they should�*accomodate* the problem by buying more hardware, increasing buffer sizes, etc.� The key with the latter approach�is to realize that you haven't fixed anything, only accomodated it by throwing resources at it.
�
Pop quiz:� Think of a parent with a spoiled child who is making a scene in public.� How do you quiet the child?� :-)
