| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> Re:Followup Question: Re: How-To or Good Practices on Code
Tracy,
Lots of luck! We use SourceSafe religiously for the developers. Care to guess what happens way too often? Change control is more of a philosophy than a software package. Proving the worth of the mindset change is easy. Getting it practiced is hard! :(
Dick Goulet
____________________Reply Separator____________________ Author: "Tracy Rahmlow" <tracy.rahmlow_at_aexp.com> Date: 11/13/2002 10:09 AM
I am looking for more details on the integration of a version control product
(sourcesafe) and a change control product such as BMC's change manager. Are
there any good sources of info relating to an optimal configuration. For
example, do you have separate project folders within sourcesafe for dev,
acceptance and prod source versions? If so, how do you deploy the change to a
target database using a product like BMC's change manager? In addition, how
are projects defined with a version control system. By entity type or project
release? For example, which layout within a version control system:
/dev/policy entry/xxxx.exe
/xxxx.sql
or
/dev/exe/xxxx.exe
/sql/xxxx/sql
or some other option? We are really struggling between a released-based structure vs an entity type. Anybody aware of any good papers describing version control and deployment for oracle objects as well as other type such as java, vb, shell scripts??
M PST Please respond to ORACLE-L_at_fatcity.com
Sent by: root_at_fatcity.com
To: "Multiple recipients of list ORACLE-L" <ORACLE-L_at_fatcity.com> cc:
The releases should be tried in the Development environment first. Then a UAT (User Acceptance Test) environment, then production. The UAT environment is usually a duplicate of the production environment. This is the environment that you implement the changes , then test to see if the changes worked and if there are any side effects. The end user , project manager, information owner, or test manager signs off that the changes were implemented correctly. Then approval is given and the change is implemented in the production environment. This is usually accompanied by some sort of change control management. Also, use some sort of source code control to keep the DML and DDL scripts in. Oracle's SCM Repository (once part of Oracle Designer), TrueChange by TrueSoft, PVCS, etc. are candidates for this.
By implementing the scripts in the UAT environment, any dependencies become
evident. Also, the developers should submit the changes in fully runnable
SQL scripts, with
appropriate comments. If the scripts are dependent upon some other script
or database object, this should be listed in the SQL file comment header,
along with the authors name and a description of the file.
Hopefully this will get you going.
RWB "Jamadagni, Rajendra" <Rajendra.Jamadagni_at_espn.com>@fatcity.com on 11/13/2002 09:29:47 AM
Please respond to ORACLE-L_at_fatcity.com
Sent by: root_at_fatcity.com
To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com> cc:
Friends ...
I have a (sort of) problem ... what are the best practices to manage code releases to production environment ...
currently we get a bunch of scripts from development team, and we release code to production on the schedule (currently twice a month). But this is not complete. The scripts we get consists of various DML and DDL statements.
We do not have a mechanism to roll-back these changes in place and I am seeking your opinion on ways to achieve these. Also we would like to implement script dependencies (which we manage manually right now) and rollback mechanism.
Are there any good practices papers? I know these would be site specific, but I am looking for common methods.
Hope I make myself clear ... (and if it matters it is Oracle 9.2 and
Forms/Reports) application.
Raj
(See attached file: ESPN_Disclaimer.txt)
(See attached file: ESPN_Disclaimer.txt)
Content-Type: text/plain; name="ReadMe.txt"; charset="us-ascii" Content-Transfer-Encoding: 7bit
The previous attachment was filtered out by the ListGuru mailing software at fatcity.com because binary attachments are not appropriate for mailing lists. If you want a copy of the attachment which was removed, contact the sender directly and ask for it to be sent to you by private E-mail.
This warning is inserted into all messages containing binary attachments which have been removed by ListGuru. If you have questions about this message, contact Postmaster_at_fatcity.com for clarification.
--IMA.Boundary.48321273010--
-- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: dgoulet_at_vicr.com Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- 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-LReceived on Wed Nov 13 2002 - 12:39:11 CST
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
- application/octet-stream attachment: ESPN_Disclaimer.txt
 |
 |