RE: Implementing Stored Procedures

hi
lisa,
we do
have staging area (dba -directory) in production  where all the scripts ...(sql,forms,reports)  are kept and with change request forms they are implemented...
if any
problems with the scripts they willl go to owner of change requester.  And We use version control (PVCS, MS visual source safe) to
track changes done to the prodecures and scripts.
<FONT face=Arial color=#0000ff

size=2> 
<FONT face=Arial color=#0000ff

size=2>naren

  <FONT face=Tahoma
  size=2>-----Original Message-----From: Yttri, Lisa   [mailto:lisa.yttri_at_cnh.com]Sent: Friday, June 01, 2001 5:02   AMTo: Multiple recipients of list ORACLE-LSubject:   Implementing Stored Procedures
  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 - <FONT   size=2>Lisa Received on Thu May 31 2001 - 17:00:26 CDT