Re: Snapshots, foreign keys, replication HELP! :)

From: Steve McDaniels <steve.mcdaniels_at_sierra.com>
Date: Wed, 10 Nov 1999 15:12:30 -0800
Message-ID: <80cu6l$f52$1@plo.sierra.com>

Since the destination is a DEV type environment, you probably don't need real-time "correctness".

What about a job (aka dbms_job.submit()) which truncates the DEV table and repopulates it once a day/week/month?

NetComrade <andreyNSPAM_at_bookexchange.net> wrote in message news:3821d470.94171773_at_news.earthlink.net...
> Hey all,
>
> We have a DEV database and PROD databases. The PROD database is
> updated daily, and we would like certain tables to be copied to our
> DEV servers. I figured snapshot is a good thing to do, especially b/c
> the tables aren't so big. But ehre is the problem...
>
> The snapshot has to have the same name as the existing table, which
> means I have to drop the existing table, and create the snapshot with
> that name. Another problem is that that table has foreign keys on it,
> and I don't know how a snapshot will behave with them...
>
> Thanx for any help.
> ---------------
> Andrey Dmitriev eFax: (978) 383-5892 Daytime: (917) 373-5417
> AOL: NetComrade ICQ: 11340726 remove NSPAM to email
>
Received on Wed Nov 10 1999 - 17:12:30 CST