Dear Richard,
These are a bunch of developers who think they are "GOD" (at-least their managers think so) ... we have learned that it is better to let them try and fail themselves rather than trying to explain them the right thing ... it works all the time. It is their database, and they own it, so if it has any problems, they suffer ... and learn.
Lather .. rinse .. repeat.
Yes, they could have done something better, but sometimes they need output in a fraction of a second ... because when "bottomline" or "clock" gets updated during a live broadcast, having 1 to 1.5 second delay is unacceptable... Most other times these developers are good ... they fight if their queries take longer than 500ms ... they try to tune and tune the code to make it right. It is only "sometimes" something like this happens.
Plus we never could reliably run dbms_jobs on 9012 on AIX 433 .. all dba related actions rely on "cron" ..
Raj
______________________________________________________
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't reflect that of ESPN Inc.
QOTD: Any clod can have facts, but having an opinion is an art!
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 10, 2002 9:13 AM
To: Jamadagni, Rajendra; Multiple recipients of list ORACLE-L
Subject: Re:RE: a PL/SQL design question.
DBMS jobs are good things for stuff that can occur totally within the database
and on a scheduled basis only. It sounds, RAJ, like your developers made a real
mess. What would have been a better idea would have been to have the trigger
update a table that the job on a scheduled basis checked for what it needed to
do.
Dick Goulet
********************************************************************This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you.*********************************************************************2
