That is exactly why a project dba should be around.
And issue guidelines (or standards, depending how thight
you want to specify it) on how to write sql.
And explain indexes and hints, execution plans and the lot.
Developers don't need to know it all, but awareness brings
a lot!
--
Frank
Dasari <sbabudas_at_ford.com> schreef in berichtnieuws
8t3vc8$ahs1_at_eccws12.dearborn.ford.com...
> Educating developers to write better SQL is far most easier but they never
> follow they have their own problems. For instance for same purpose many
> developers write same SQL in different styles confusing Oracle. Please do
> not call this as bad design of application, but merely an issue of
> controlling all this
> to make a DBA life easier. Monitoring for time consuming SQLs and tuning
is
> a continuous process anyway.
> Can I say something like a .sql file with all the SQL statements written
by
> the developers called SQL library, If they want to write a SQL pl. check
in
> this file
> make sure one is not available for the purpose and append into this file
and
> a DBA frequently monitors this file for any new SQL's that require basic
> tuning.
> Does this make sense.
> How you'll do this, I would be very grateful if you could share some
> thoughts / ideas.
>
> TIA
> Dasari
>
>
>
Received on Tue Oct 24 2000 - 09:19:51 CDT
