Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Database programming standards

RE: Database programming standards

From: Deen Dayal <>
Date: Mon, 07 Jun 2004 10:53:55 -0400
Message-id: <>

Hi all,
God morning and thank you all very much for a valuable discussion on this topic.

With this we will be able to add some thing meaningful in our RFP which will help us in a long way.

I am fortunate to be a part of this list.


-----Original Message-----

From: [] On Behalf Of Michael Thomas
Sent: Sunday, June 06, 2004 9:11 AM
To: Multiple recipients of list ORACLE-L Subject: Re: Database programming standards

Hi deen,

This may help you with your RFP, from an Oracle DBA's perspective. Sorry if I'm a little slow to reply.

-----Original Message-----

From: deen dayal [mailto:deen.dayal_at_xxxxxxxxxxxxxxx] Sent: Wednesday, June 02, 2004 5:26 PM
To: oracle-l_at_xxxxxxxxxxxxx
Subject: Database programming standards

Hi all,

We are in the process of preparation of a RFP for a big project; it is going
to be developed in J2EE, do not know which app server we are going to use (
probably SUN Iplanet server ), Oracle 9i is the back end.

I am looking for some database programming standards to be written up in RFP
so that we maintenance team can reduce the amount of mess to deal with after
vendor leaves.
----------END QUOTE----------
Why not include in the RFP SLA that "Any off the shelf (OTS) application that does *not* allow Oracle to support RI, nor triggers, nor stored procedures, must *guarantee* RI and equivalent performance/scalability without additional maintenance or productivity costs"?

  1. One form of *guarantee* might be to refund the cost of DBA work to analyze and delete duplicate records, or pay to perform database optimization/scalability testing and updates.
  2. Another example, pay the consulting expenses and lost productivity penalty to *fix* RI in the OTS application.
  3. Finally, pay for legal and business expenses to recover costs of failed RI in the OTS application, since the OTS vendor did not support running RI features in Oracle. How about paying expenses to recover duplicate payments generated erroneously?

Unfortunately, these are some actual experiences I wish were included in our project RFP up-front.

You can likely think of a few similar ideas. ;-)

HTH. Regards,

Mike Thomas                          

Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.

Please see the official ORACLE-L FAQ:

To unsubscribe send email to: put 'unsubscribe' in the subject line.

Archives are at FAQ is at

Please see the official ORACLE-L FAQ:

To unsubscribe send email to: put 'unsubscribe' in the subject line.

Archives are at FAQ is at
Received on Mon Jun 07 2004 - 09:50:56 CDT

Original text of this message