Re: Dev database/production database

Whoa. I think you need one more environment. You might want to have a "user's acceptance" database. This is a copy of the production database structures. You need to package up your changes that you made to your development database. The problem comes when you need to migrate those changes to a production environment. You need a series of scripts that will modify production tables and other objects so that they look like your development database. Your production system is the last place you want to try this out. An acceptance environment is where you can trap migration script errors.

Desktop DBA from Computer Associates (formerly Platinum Technology) had a database compare facility. It could generate a set of differences scripts. You could do the same thing by looking at the data dictionaries of both database. But by the time you get your script debugged, you could have bought DDBA. But always test those migration scripts against a copy of your production environment. Think of it as a dress rehearsal.

--rn.

Sam Jordan <sjo_at_spin.ch> wrote in message news:379C3A0C.7809CC84_at_spin.ch...
> Hi
>
> I am right now trying to figure out how to solve the problem
> of having a development environment and a production environment.
> For the software parts it wasn't difficult, and now I'm focusing
> on the Oracle 8 database. I don't have experience concerning
> dev/production databases, so I hope to learn about it from other
> people.
Received on Sun Aug 01 1999 - 16:11:02 CDT