Re: deployment of new stored objects without a local dba

In article <ADG9Taomj0_at_dwayne.FreeNet.Kiev.UA>, dwayne_at_dwayne.FreeNet.Kiev.UA says...

>I am looking for input from people on how they do deployment of new versions
>of DB packages, triggers etc. if you don't have the luxury of a local DBA.
>The people there will be trained on the network s/w, but nothing on the DB :(
>
>We are currently readying for deployment, to fourteen sites (we currently
>only have one pilot office). What we want to do is create an idiot-proof
>install program that will install the new forms, reports, run DDL and SQL
>scripts etc.

Why not just do all the stored object management from one site via the miracle of Sql*Net? Thats all we do (nine DBs spread over five machines on three sites). Then just ftp or whatever any files you need over. If you adhere rigorously to Oracles OFA layout, you can even do DB upgrades by just compressing up the new distribution, ftp it to your remote machine, decompress & run orainst. Some of this stuff may not work if you aren't on Unix of course;)

Anything that can be installed via SQL, can be installed remotely, assuming the different sites are networked.

>I am part way there (to the last point). You can only run scripts with a
>userid/password string, which we obviously don't want to include in our
>installation disks. Also this would mean we need to use the same password at
>each site.

Cheers.
Martin. Received on Wed Nov 20 1996 - 00:00:00 CST