Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Implementing Stored Procedures

RE: Implementing Stored Procedures

From: <Diana_Duncan_at_ttpartners.com>
Date: Thu, 31 May 2001 13:09:36 -0700
Message-ID: <F001.00316830.20010531120935@fatcity.com>

There's an excellent tool by the company Kintana that automates the deployment of software (which can include stored packages and procedures, as well as shell scripts, SQL*Loader, whatever). The developer creates a "release" with the file names and version numbers in PVCS or ClearCase, and the tool extracts and runs the approprate files on other servers as determined by "workflows" -- so you can use this tool to go from dev to QA to production, etc. Very nice tool, I'd highly recommend it. And no, I am not affiliated, just a happy user.

Diana Duncan
TITAN Technology Partners
One Copley Parkway, Ste 540
Morrisville, NC 27560
VM: 919.466.7337 x 316
F: 919.466.7427
E: Diana_Duncan_at_ttpartners.com

                                                                                       
                                
                    "Bala, Prakash"                                                    
                                
                    <prakash.bala_at_cin        To:     Multiple recipients of list 
ORACLE-L <ORACLE-L_at_fatcity.com>       
                    gular.com>               cc:                                       
                                
                    Sent by:                 Fax to:                                   
                                
                    root_at_fatcity.com         Subject:     RE: Implementing Stored 
Procedures                           
                                                                                       
                                
                                                                                       
                                
                    05/31/2001 02:46                                                   
                                
                    PM                                                                 
                                
                    Please respond to                                                  
                                
                    ORACLE-L                                                           
                                
                                                                                       
                                
                                                                                       
                                




Lisa,

This is what we did in my last project:

  1. Developers had access to the application schema where they created and modified procedures/functions/triggers as needed
  2. After their unit testing is done, the QA team would test it using the front-end application.
  3. Once QA team approves the new/enhanced functionality, the developers would check in the code using PVCS and notify the DBA vith the PVCS version number and the object name.
  4. The DBA tracks the object version numbers along with the application releases and implements the necessary changes in the production box. Developers did not have any rights on the production box.

HTH! Prakash

-----Original Message-----
Sent: Thursday, May 31, 2001 1:02 PM
To: Multiple recipients of list ORACLE-L

Hi -

I'd like some advice on implementing stored procedures containing application logic (ie. written by developers). We have several applications
where the developers use stored procedures for much of their coding. We let
the developers create or replace their procedures in a development environment under their own schema (with access to all application tables, etc.) to test the logic, but it currently requires a DBA to implement the proc under the application schema. It has gotten to be a very time-consuming job. We don't want to give out the schema owner password to the developers, nor do we know of a way they could add them as the schema owner without giving them more privileges than we want.

I am curious of how others are handling stored procedure additions and modifications. Do you somehow allow developers this access? If so, how do you restrict them from damaging other things? If not, does the DBA do it? Does anyone have an automated way? Also, do you keep track of the original "source code" for the procedure, or do you extract it out of the database as needed?

Thanks so much for your input -
Lisa

--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Bala, Prakash
  INET: prakash.bala_at_cingular.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L

(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: Diana_Duncan_at_ttpartners.com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Thu May 31 2001 - 15:09:36 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US