|
|
|
|
|
|
|
Re: Time taken in export and import [message #543169 is a reply to message #543156] |
Mon, 13 February 2012 04:45   |
Database admin
Messages: 365 Registered: September 2006 Location: india
|
Senior Member |
 
|
|
Sorry, i reviewed my answer and found one mistake in export.Please find the below corrections.
By reading your answers, i would say it is good practice to export objects as it is, as the indexes and
constraints are y by default and do 2 steps for import with
1.indexes=n and constraints=n , rows=y
2.indexes=y and constraints=y and rows=no which will faster data insertion and saves time.
Thank you
[Updated on: Mon, 13 February 2012 04:47] Report message to a moderator
|
|
|
|
Re: Time taken in export and import [message #543184 is a reply to message #543171] |
Mon, 13 February 2012 05:37   |
ThomasG
Messages: 3212 Registered: April 2005 Location: Heilbronn, Germany
|
Senior Member |
|
|
It's not really possible to say if it's "good practice" or not in general.
It *might* be good practice, if you want to make the downtime shorter, and you are able to put the application online again without some of the indexes.
For example, I do upgrades on an application where there are a few tables with big indexes which are only used during day-end processing. So I can put the application online again for the users, and re-build that specific indexes while the users are already working again. But just blindly changing the export/import the way you suggest is not really a good idea. The overall process will definitely not be faster.
|
|
|
|
|
|
Re: Time taken in export and import [message #543196 is a reply to message #543195] |
Mon, 13 February 2012 06:40   |
ThomasG
Messages: 3212 Registered: April 2005 Location: Heilbronn, Germany
|
Senior Member |
|
|
And if that doesn't work:
Buy faster hardware.
If there would be a "guaranteed" and "simple" technique to make export/import faster, then that technique would have been already implemented in the standard export/import
|
|
|
|