Re: Importing Databases

 Instead of dropping the user, you could just disable the constraints on the tables and truncate the data out from them. Then use the IGNORE=Y parameter on import so it won't error because the objects already exist. Of course, this approach works on the assumption that you have not changed any of the table definitions between the databases...

Steve Phelan.

Scott Metro wrote in article ...

>I need to periodically synchronize a development database with a production
>database. I have been doing this by exporting (either full or user) from
>the production database and then dropping the user in the development
>database and then importing the user into the dev. database.
>
>The two databases are not connected. Basically, when I'm at a client, I
>export the database and when I get back I use the above process to import
>it.
>
>Is this the best way, or is there a simpler way, that doesn't require
>dropping the user first. One problem with my way, is that the triggers
>don't seem to be coming over, and I need to recreate them manually.
>
>Thanks in advance,
>smetro_at_world.std.com
>
>
Received on Thu Jul 31 1997 - 00:00:00 CEST