Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

pl/sql application build & release

25 views
Skip to first unread message

Jeremy

unread,
May 1, 2012, 8:41:37 AM5/1/12
to
Hi just wondering if anyone could shed any light on good tools for
managing the build and release of PL/SQL-based applications.

We are using SVN and a mix of SQL*Developer & PL/SQL Developer & Textpad
for code development.

We manually build scripts for DDL changes for each release and manually
build scripts to compile packages, triggers etc. and am wondering if
there are any tools that any of you are using that assist in this.

We use SVN branches/tags for each release but have to eb able to apply
this release to multiple target databases.

--
jeremy

John Hurley

unread,
May 1, 2012, 9:08:44 AM5/1/12
to
jeremy:

# Hi just wondering if anyone could shed any light on good tools for
managing the build and release of PL/SQL-based applications.

I tend to do this manually using at times schema comparison tools
( like Toad does with DBA module available ) for double/sanity
checking. I like to end up with shell scripts that I can execute with
a couple of parameters ( including ORACLE_SID ) so that the exact same
script base goes against different instances.

Both Toad and SQL Navigator ( both from Quest although I have not used
SQL Navigator for like 10 years ) have somewhat customizable tools
that can produce scripts to synchronize schemas. Obviously you have
to be extremely careful in looking at and testing/verifying any output
from tools generating stuff like that.

Oracle also has some of its own tools ( licensable packs I think )
that play in this area but no experience in the last 10 years using
any of that.

Hope this helps somewhat and I am sure some other people will report
back what they are doing in their environments.

Mladen Gogala

unread,
May 1, 2012, 11:16:19 AM5/1/12
to
On Tue, 01 May 2012 13:41:37 +0100, Jeremy wrote:


> We are using SVN and a mix of SQL*Developer & PL/SQL Developer & Textpad
> for code development.

Textpad??? Why not Vim?



--
http://mgogala.freehostia.com

Jeremy

unread,
May 1, 2012, 11:32:42 AM5/1/12
to
In article <jnouo3$aqv$1...@solani.org>, gogala.REMO...@google.com
says...
>
> On Tue, 01 May 2012 13:41:37 +0100, Jeremy wrote:
>
>
> > We are using SVN and a mix of SQL*Developer & PL/SQL Developer & Textpad
> > for code development.
>
> Textpad??? Why not Vim?

Tend to use that for cleaning the kitchen.

--
jeremy

Mladen Gogala

unread,
May 1, 2012, 3:35:48 PM5/1/12
to
On Tue, 01 May 2012 16:32:42 +0100, Jeremy wrote:

>> Textpad??? Why not Vim?
>
> Tend to use that for cleaning the kitchen.

Touche! However, my question wasn't just tongue in cheek, Vim has a
package that can do PLSQL formatting, albeit not very well. SciTE has it,
too.



--
http://mgogala.byethost5.com

Jeremy

unread,
May 1, 2012, 3:44:31 PM5/1/12
to
In article <jnpduk$q1v$1...@solani.org>, gogala...@gmail.com says...
>
> On Tue, 01 May 2012 16:32:42 +0100, Jeremy wrote:
>
> >> Textpad??? Why not Vim?
> >
> > Tend to use that for cleaning the kitchen.
>
> Touche! However, my question wasn't just tongue in cheek, Vim has a
> package that can do PLSQL formatting, albeit not very well. SciTE has it,
> too.

Well we are spoilt for text editors really; but that's not really what
am I seeking suggestions for (thanks anyway).

Looking for the build & deploy tools really.

--
jeremy

Jeremy

unread,
May 3, 2012, 4:01:37 AM5/3/12
to
In article <7f94df17-94ac-42f7-8f66-ccc8f5fc5c02
@e42g2000yqa.googlegroups.com>, johnth...@gmail.com says...
>
> Hope this helps somewhat and I am sure some other people will report
> back what they are doing in their environments.
>

Perhaps they're being shy.

--
jeremy
Message has been deleted

Jeremy

unread,
May 3, 2012, 4:54:11 AM5/3/12
to
In article <4fa246a1$0$10734$5b6a...@news.zen.co.uk>,
dontw...@nowhere.invalid says...
> Or perhaps they just use manual scripts too? Fwiw, that's what we've
> always done, & it's mostly worked ok. However for reasons I won't bore
> you with, we've now split the app into two schemas; one for the tables,
> sequences & triggers, t'other for everything else.
>
> So subject to hitting any problems with the process, future releases
> will be done by exporting the 'code' schema from the 'release' DB &
> importing it on the destinations[1]. Table changes & triggers will
> still be done with the manual scripts. So still no tools involved, but
> an alternative approach to throw into the mix.
>
> [1] Currently 12 dotted around the UK & Ireland.

ta

--
jeremy

Mark D Powell

unread,
May 3, 2012, 10:17:58 AM5/3/12
to
We also just use manual tools to make pl/sql and sqlplus script changes. For our official source for database objects we store after images of the code. That is each time a table is altered (column added, index added, etc) or a package is modified we generate a new code listing via home-grown dictionary extract (generate DDL) scripts and store the new source in sccs.

You can diff the most recent source file verse the previous version to determine the change made. Developers are required to provide the DDL to apply the change to system test and later production.

All object DDL that are dropped by Oracle when you drop a table are stored as part of the table source while independent objects such as functions, procedures, packages, and sequences have their own source members.

HTH -- Mark D Powell --

Mladen Gogala

unread,
May 3, 2012, 3:52:06 PM5/3/12
to
On Thu, 03 May 2012 07:17:58 -0700, Mark D Powell wrote:

> store the new source in sccs.

SCCS?



--
http://mgogala.freehostia.com

TheBoss

unread,
May 3, 2012, 4:22:22 PM5/3/12
to
Mladen Gogala <gogala.REMO...@google.com> wrote in news:jnunl6$6vo
$1...@solani.org:

> On Thu, 03 May 2012 07:17:58 -0700, Mark D Powell wrote:
>
>> store the new source in sccs.
>
> SCCS?
>

Probably the oldest commercial revision control system, except may be
CCC/Harvest (now CA Software Change Manager). See:

< http://en.wikipedia.org/wiki/Source_Code_Control_System >
< http://en.wikipedia.org/wiki/CA_Software_Change_Manager >

--
Jeroen

joel garry

unread,
May 3, 2012, 4:22:56 PM5/3/12
to
On May 3, 12:52 pm, Mladen Gogala <gogala.REMOVETHISmla...@google.com>
wrote:
man sccs works on my system.

(but I use a simpler structure from the app vendor)

jg
--
@home.com is bogus.
http://www.zdnet.com/blog/btl/oracle-google-lawyers-split-hairs-over-more-jury-instructions/76163

Mladen Gogala

unread,
May 7, 2012, 4:41:07 PM5/7/12
to
On Thu, 03 May 2012 20:22:22 +0000, TheBoss wrote:


> Probably the oldest commercial revision control system, except may be
> CCC/Harvest (now CA Software Change Manager). See:
>
> < http://en.wikipedia.org/wiki/Source_Code_Control_System >
> < http://en.wikipedia.org/wiki/CA_Software_Change_Manager >
>

I never used SCCS. I used RCS, CVS, SVN, ClearCase and GIT but never
SCCS. It sounds like something from the stone age, brought to America by
the Clovis people, along with flint axes and spear tips.



--
http://mgogala.freehostia.com
0 new messages