Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
faq:migration-toolkit:optimize-migration-process-large-tables [2019/06/12 00:42]
127.0.0.1 external edit
faq:migration-toolkit:optimize-migration-process-large-tables [2019/07/25 11:25]
darya.prikhodkina
Line 1: Line 1:
-====== How to Optimize the Migration Process for Large tables ​======+====== How to Optimize the Migration Process for Large Tables ​======
  
 There are several ways to reduce migration time and speed up the migration process.\\ There are several ways to reduce migration time and speed up the migration process.\\
-  - If there have been no problems during the export you can turn off trace mode. Thus there will be no trace generation which will help to reduce migration time.\\ +  - If there have been no problems during the export you can disable the trace mode. Thus there will be no trace generation which will help to reduce migration time.\\ 
-  - You can split the data migration ​into parts and run them simultaneously in our tool. This can be done in two ways:\\+  - You can split the data into parts and run the migrations ​simultaneously in our tool. This can be done in two ways:\\
     - **Using Data Options**     - **Using Data Options**
     - **Using the Queries**     - **Using the Queries**
Line 9: Line 9:
 === Using Data Options === === Using Data Options ===
  
-When you select “Data Options” tab for tables you see Edit boxes for the start row and the number of rows to be exported (like below). By varying these numbers in separate instances of Wizard (like 1-5000, 5001-10000, etc.) you can run the migration of different parts of data simultaneously.+When you select “Data Options” tab for tables you see Edit boxes for the start row and the number of rows to be exported (please see below). By varying these numbers in separate instances of SQLWays ​Wizard (like 1-5000, 5001-10000, etc.) you can run the migration of different parts of data simultaneously.
  
 {{:​faq:​migration-toolkit/​data_options.png|}}\\ {{:​faq:​migration-toolkit/​data_options.png|}}\\
  
-Pleasealso note that you should uncheck “Generate DDL” option for processes other than the first one to avoid error of table existence. In this case only data will be migrated.+Please also note that you should uncheck “Generate DDL” option for the processes other than the first one in order to avoid the error of table existence. In this case only data will be migrated.
  
 {{:​faq:​migration-toolkit/​ddl_options.png|}}\\ {{:​faq:​migration-toolkit/​ddl_options.png|}}\\
Line 20: Line 20:
 === Using the Queries === === Using the Queries ===
  
-You can export data according to unique index or primary key or any other query condition. To perform this in Wizard please select “Use Query” in combo-box ​like below. ​+You can export data according to unique index or primary key or any other query condition. To perform this in SQLWays ​Wizard please select “Use Query” in combo-box ​shown below. ​
 Using this option you can write your own query to select data. DDL statement will be generated according to the selected columns. ​ Using this option you can write your own query to select data. DDL statement will be generated according to the selected columns. ​
-Table name will be the same as in FROM clause. But we advise you to create empty tables first and then to do the migration of data this way.  +Table name will be the same as in FROM clause. But we advise you to create empty tables first and then to perform ​the migration of data.  
-You’ll get errors when trying to create a table but data will be loaded ​fine.+You’ll get errors when trying to create a table but data will be loaded ​correctly.
  
 {{:​faq:​migration-toolkit/​use_queries.png|}}\\ {{:​faq:​migration-toolkit/​use_queries.png|}}\\