Re: Shared Sequencers

Ed,

Thanks for your help and sorry for the lack of information. I guess I was in a hurry that day, and after looking back the question was very vague.

To clarify:

Our "internal users" (customer admins.) are creating data on the Staging DB, because we don't want them working directly on Production. When this data is correct it is "published" to the Production DB.

There may be cases when there is a code change and we want to pull "live" data back for testing against the new code on Dev.

Also, QA may test new code by creating data for an actual customer. If QA needs to test new code why not have them create a valid dataset. In this case we want to move data from QA into Production.

There is also some data that is created by the end user of the application on Production. This data may need to be moved back to dev. to test against new code or to track problems customers may be having.

Since there are sequences used on many of the tables and the data is highly interrelated (i.e., for one object the data is stored across 12 tables) we basically need to be able to move data anywhere in the system hierarchy without fear of breaking a constraint.

I hope this makes more sense rather than adding to the confusion.

Thanks again.
--Nathan

ed.prochak_at_magicinterface.com (Ed prochak) wrote in message news:<4b5394b2.0308010454.722c84de_at_posting.google.com>...
> nathan_burleson_at_yahoo.com (Nathan Burleson) wrote in message news:<fcb2e0b8.0307311252.10b2ef1a@posting.google.com>...
> > Hello,
> >
> > Are there any issues with sharing sequences across databases? I want
> > to be able to move data from Dev. to QA to Staging to Production and
> > back, but I need to keep sequences intact.
> >
> > BTW: Using Oracle 8i
> >
> > Thanks in advance for any help.
> > --NB
>
> Dev->QA->Production and back?
>
> If you want to risk hitting the production system I can imagine having
> DB links to the production box where the real sequence is kept. But
> then DEV and QA testing will not be realistic since access to the
> sequence will be thru the like and thus slower.
>
> Are you sure that's what you want?
>
> In similar conditions (conversions), I've used assigned ranges. So
> test conditions for both Dev. and QA are similar, and data can still
> be merged into production. (you really want to take data from Dev into
> prod.?? What kind of system needs that?)
>
> ((Why do these questions always sems to lack sufficient context?))
>
> Maybe another idea: how is this data being moved between systems? You
> could fix up the sequences during the moves up the ladder. This would
> be incremental data so extra processing might not be too heavy.
>
> Moving the data back down might involve taking full exports from prod
> to QA and Dev. at least of those tables involved in the sequences.
>
> I still don't like moving data that developers create into the
> production DB.
>
> Did any of these suggestions help?
>
> Ed Prochak
> Magicinterface, Ltd.
> 440-498-3700
Received on Mon Aug 04 2003 - 20:23:40 CEST