On 06/23/2011 08:19 PM, John Hurley wrote:
[snip!]
Because SQL is so well made and powerful, everyone
can get it to run (see above...)
So, if it does not run, it must be the database.

C'mon my dear Watson! It's soooooo elementary.

--

Regards,

Frank van Bortel

On 06/24/2011 12:40 AM, joel garry wrote:
Oh sh*t - this is about MicroSoft effing Server? I should not
have commented at all.

--

Regards,

Frank van Bortel

Neil:

# The point I am making - life is complicated these days.

It gets somewhat simpler as you gain experience and get older.
Patterns and underlying principles often emerge out of the
"complications".

# As a developer, you may touch upon a wide variety of technolgies
(every piece of software interacting with most of the others). There
just isn't the time to be an expert in each.

Any serious enterprise development effort that does not take the time
to understand relevant details about the database platform that it is
going to be using "under the covers" is probably going to compromised
unless the developers ( or at least senior technical architect ) take
the time to do their homework.

Scaleable high performing applications do not appear just because you
use a wide variety of technologies. Realistically the more different
technologies you throw into the mix the more likely you start swimming
around in circles.

# Sometime you want it to just start up without tuning (whatever that
means, wow).

Is that like start coding before doing a database design?

Neil:

# I don't know the full answer, as I am not an Oracle admin, but one
example of tuning would be the running of performance tests and adding
an index to speed up a query on a table.

Theoretically by the time when you create a table you should have a
good idea of what queries are going to be run against the table.

That's not really tuning ... just application and database design.

Developers should know how to use dbms_xplan effectively.

Performance testing and benchmarking should also be part of the
development design efforts.

On Jun 29, 5:33*pm, John Hurley <hurleyjo... (AT) yahoo (DOT) com> wrote:
Patterns and underlying principles just don't cut it. Computers tend
to deal in binary - they tend to expect something precise rather than
a general ideology or a well-meaning concept.

That is not what I am saying at all, you misunderstood.
To start learning an application it would be nice for it to actually
start up after selecting defaults from the installer.
I assume you weren't fed Oracle documentation as a foetus?

Well, that's how the world is I'm afraid. It's full of complexity.
I am not throwing more technologies into the mix, far from it - I am
trying to support the most commonly used applications.
I would love the whole world to use one database (so long as it's not
Oracle :-)

Did you fully tune your first Oracle database before touching it?
Do you realise how crazy that sounds?

Not really. Unless you are psychic. That's why they call it software
development - stuff changes, gets redesigned etc etc.

Whatever you would like to call it.

Who said I was doing any development of any database with Oracle? My
development has nothing to do with Oracle design itself.

I am to used to SQL server I guess.