Re: Best way to refresh table from different instance

Hi All,

 We always use export and import unless it's going to be a regular (weekly?) occurance. You would do an export on the production DB (don't know what kind of size you are talking about) and import just that schema or table on the development DB. We do this frequently. At least then you don't have to configure SQLNet connectivity. Export will copy (and recreate) all indices, etc...

 Good luck,
 Bill

 If this posting has been useful, return the favor by visiting http://dbamon.com . There is a free tool called orastat that you can download which will automate many commonly performed Oracle tasks/queries.

--
Bill Border
Agilent Technologies
bb22_at_uswest.net
Low-Cost, UX-Based Oracle/Informix Monitor: http://dbamon.com
andyho99_at_yahoo.com wrote in message <8t1opt$67v$1_at_nnrp1.deja.com>...


>I wonder what's the best way to refresh development tables from

>production database. I used to drop table xyz; then, cretae table xyz

>as select * from xyz_at_prod. However, someone told me that the indexes

>will be lost.

>

>Is there a better way to achieve what I want?

>

>Thanks, Andy

>

>

>Sent via Deja.com http://www.deja.com/

>Before you buy.