Re: refreshing from production

From: Diana Bonham <diana_at_fnal.gov>
Date: Thu, 04 Oct 2001 16:49:59 -0500
Message-ID: <3BBCD987.6000704@fnal.gov>

i asked a few months back, but I guess I stumped everyone. My question then was "how to refresh a database with a SAMPLING of production data" Our production database is just getting too big to easily do it with export/import, and takes up more disk space than we care to use. Does anyone know of a 3rd party product to take a sampling of a database, perhaps giving it a "master table" to take the sample from, and which follows all the foreign key constraints to child tables all the way down to take the corresponding rows from them? Sounds like a tall order....   Anyone ever written a program to do this?

  Diana

Nuno Souto wrote:

> On Tue, 04 Sep 2001 18:38:46 GMT, "Terry Dykstra"
> <dontreply_tdykstra_at_cfol.ab.ca> wrote:
>
>

>>Or delete the development database, copy over the production db and then use
>>'backup control file to trace' to rename the copied database into develop.
>>
>>--
>>

>
> The backup/restore thing works, but it also copies all uids/pwds from
> production to development. It's advisable to have a step added that
> changes at least some passwords and disables most of the remaining
> production users.
>
> Also, be aware that you're copying the *entire* production setup.
> Potentially, you are copying extensive rollback and tremporary
> tablespaces that support the full production load of users. For large
> loads of users (or large production databases), these two may be quite
> large. You may not require these in development. At the very least,
> you may end up with considerable wasted disk space.
>
>
> Cheers
> Nuno Souto
> nsouto_at_optushome.com.au.nospam
>
Received on Thu Oct 04 2001 - 16:49:59 CDT