| Time taken in export and import [message #543070] |
Mon, 13 February 2012 01:27  |
|
|
Hi,
When i do a table export , it got over in 30 mins.When i do import using same dump file
(that was created in 30 mins), its taking more than 30 mins .
Can you guys tell the reason as why the import is taking more time than the export time ?
Thank you
|
|
|
|
|
|
| Re: Time taken in export and import [message #543097 is a reply to message #543071] |
Mon, 13 February 2012 02:20  |
|
|
Thank you for your explanations.
Quote:because "indexes data" are not exported but indexes are recreated and so on.
When indexes data are not exported then how do you say the indexes are recreated and so on.
you mean indexes are recreated during import ?
Can you please clarify my doubts?
Regards
|
|
|
|
|
|
| Re: Time taken in export and import [message #543127 is a reply to message #543104] |
Mon, 13 February 2012 03:16 |
|
|
By reading your answers, i would say it is good practice to export objects with indexes=n and do 2 steps of import with
1.indexes=n and constraints=n , rows=y
2.indexes=y and constraints=y and rows=no (which is the default ) which will faster data insertion and saves time.
Please clarify my points and you can add some more points if you want (just want to know more about it).
Thank you
|
|
|
|
|
|
|
|
| Re: Time taken in export and import [message #543169 is a reply to message #543156] |
Mon, 13 February 2012 04:45 |
|
|
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: 2893
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: 2893
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
|
|
|
|
|
|
] 
Members
Search
Help
Register
Login
Home
