Re: HELP!!! HORRIBLE ARCHITECTURE

Paula,

You are getting some good advice. On the practical side, as a stopgap method until better changes are made, you might consider export/import to clone the data. Since you mention that the database is large, this may not work out, but I would suggest you investigate what it would take to export/import at least some of the schemas. At the very least, it might help you understand how entangled the schemas are. You might wind up asking just what they really need refreshed. Also, you can export based on a query which is helpful if the table is large but they only need recent data for test purposes.

    This certainly isn't ideal for refreshing test databases, but I think your only alternative is to get down and dirty with these schemas, both to keep things together in the short term as well as evolve this system to the future. It sounds like you're going to end up as the negotiator between the needs to the different groups, so the ability to export/import may add some flexibility. But use it judiciously. Otherwise, instead of the groups working out a compromise, you'll end up working nights and weekends to keep everybody happy.

Dennis Williams

--
http://www.freelists.org/webpage/oracle-l