Differences

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

--- faq:migration-toolkit:utilities-to-make-import [2019/06/13 17:59]
127.0.0.1 external edit
+++ faq:migration-toolkit:utilities-to-make-import [2019/09/20 11:50]
darya.prikhodkina
@@ Line 1: / Line 1: @@
-====== What Utilities are Used in MnMTK to Perform Import ======
+====== Which Utilities are Used in Ispirer MnMTK to Perform Import ======
-When migrating from one database into another database using SQLWays Wizard tool, it is possible to execute the import process automatically. To do that you need to know about the utilities that will be used to execute import process.
+When migrating from one database into another database using SQLWays Wizard tool, it is possible to execute import process automatically. To do that you need to know about the utilities that will be used to in this process.
-SQLWays Wizard generates a .bat script for each converted object. In such a script you can find a command to the utility that will be used to perform import process. During import process the tool just runs this command to the native utility and then the utility itself connects to the target database and tries to import the converted sql code into the target database.
+SQLWays Wizard generates a .bat script for each converted object. In such script you can find a command to the utility that will be used to perform import process. During import process the tool will just run this command to the native utility and then the utility itself will connect to the target database and try to import the converted sql code into it.
-For each target database SQLWays Wizard generates commands to different native utilities. Please also note that SQLWays Wizard doesn't use any third-part tools or utilities to perform import. It generates commands only for native utilities of the target database that are provided by the RDBMS vendors.
+For each target database SQLWays Wizard generates commands to their native utilities. Please also note that SQLWays Wizard doesn't use any third-part tools or utilities to perform import. It generates commands only for the native utilities of the target database that are provided by the RDBMS vendors.
-In order to generate correct command lines to the required utilities we need to provide a path to the folder that contains required utilities in the "**Bin Directory**" option. This option can be found on the "**Specify Import Options**" page of SQLWays Wizard Tool:
+In order to generate correct command lines to the required utilities, in the "**Bin Directory**" option we need to provide a path to the folder that contains required utilities. This option can be found on the "**Specify Import Options**" page of SQLWays Wizard Tool:
-{{:faq:migration-toolkit/bin_dir.png|}}
+{{:faq:migration-toolkit/bin_dir.png?800|}}
 \\
@@ Line 17: / Line 17: @@
 ===== Databases and Utilities =====
-==== Oracle ====
+===== Oracle =====
 To perform import into Oracle database in the Bin directory Option we need to specify a path to the folder which contains //**sqlldr.exe**// and //**sqlplus.exe**// utilities. By default these utilities are located in the directory like: **c:\app\[user_name]\product\[DB_Version]\client_1\BIN\**. Otherwise you can find them in the directory specified during the installation process of Oracle database.
@@ Line 28: / Line 28: @@
 To be able to perform import into Oracle you have to tune the TNS service name and provide this name on the "Choose a Target Database" page of SQLWays Wizard tool. You can learn how to tune the TNS name in this article: [[http://wiki.ispirer.com/sqlways/users-guide/setting-up-database-connection/oracle/tns-service-name| How to Tune the TNS Service Name For Oracle]]
-==== Microsoft SQL Server ====
+===== Microsoft SQL Server =====
 For Microsoft SQL Server you need to specify a path to the folder that contains //**bcp.exe**// and //**sqlcmd.exe**// native utilities. By default these utilities are located in the directory like: **c:\Program Files\Microsoft SQL Server\[DB_Version]\Tools\Binn\**. Otherwise, you can find them in the directory specified during the installation process of Microsoft SQL Server database. You can also check the location of these utilities in the Management Studio installation directory.
@@ Line 35: / Line 35: @@
-==== Azure SQL Data Warehouse ====
+===== Azure SQL Data Warehouse =====
 For Microsoft SQL Data Warehouse you need to specify a path to the folder containing //**bcp.exe**// and //**sqlcmd.exe**// native utilities. By default these utilities are located in the directory like: **c:\Program Files\Microsoft SQL Server\[DB_Version]\Tools\Binn\**. Otherwise, you can find them in the directory specified during the installation process of Microsoft SQL Server database. You can also check the location of these utilities in the Management Studio installation directory.
@@ Line 42: / Line 42: @@
-==== Azure SQL Database ====
+==== Azure SQL Database =====
 For Microsoft Azure SQL Database you need to specify a path to the folder containing //**bcp.exe**// and //**sqlcmd.exe**// native utilities. By default these utilities are located in the directory like: **c:\Program Files\Microsoft SQL Server\[DB_Version]\Tools\Binn\**. Otherwise, you can find them in the directory specified during the installation process of Microsoft SQL Server database. You can also check the location of these utilities in the Management Studio installation directory.
@@ Line 49: / Line 49: @@
-==== IBM DB2 ====
+===== IBM DB2 =====
 For IBM DB2 database you need to specify a path to the folder containing //**db2.exe**// native utility. By default this utility is located in the directory like: **c:\Program Files (x86)\IBM\SQLLIB\BIN\**. Otherwise, you can find it in the directory specified during the installation process of DB2 Data Server Client.
@@ Line 57: / Line 57: @@
-==== IBM Informix ====
+===== IBM Informix =====
 For Informix database you need to specify a path to the folder containing //**dbaccess.exe**// native utility. By default this utility is located in the directory like: **c:\Program Files (x86)\Informix Client-SDK\bin\**. Otherwise, you can find it in the directory specified during the installation process of Informix SDK Client.
@@ Line 64: / Line 64: @@
-==== IBM Netezza ====
+===== IBM Netezza =====
 For Netezza database you need to specify a path to the folder containing //**nzsql.exe**// native utility. By default this utility is located in the directory like: **C:\\Program Files (x86)\\IBM Netezza Tools\\Bin\**. Otherwise, you can find it in the directory specified during the installation process of IBM Netezza Client.
@@ Line 71: / Line 71: @@
-==== MySQL ====
+===== MySQL =====
 For MySQL database you need to specify a path to the folder containing //**mysql.exe**// native utility. By default this utility is located in the directory like: **c:\Program Files (x86)\MySQL\MySQL Workbench 6.1 CE\**. Otherwise, you can find it in the directory specified during the installation process of MySQL database.
@@ Line 78: / Line 78: @@
-==== MariaDB ====
+===== MariaDB =====
 For MariaDB database you need to specify a path to the folder containing //**mysql.exe**// native utility. By default this utility is located in the directory like: **c:\Program Files (x86)\MySQL\MySQL Workbench 6.1 CE\**. Otherwise, you can find it in the directory specified during the installation process of MySQL Workbench.
@@ Line 85: / Line 85: @@
-==== Amazon Aurora (MySQL Compatible) ====
+===== Amazon Aurora (MySQL Compatible) =====
 For Amazon Aurora database you need to specify a path to the folder containing //**mysql.exe**// native utility. By default this utility is located in the directory like: **c:\Program Files (x86)\MySQL\MySQL Workbench 6.1 CE\**. Otherwise, you can find it in the directory specified during the installation process of MySQL Workbench.
@@ Line 91: / Line 91: @@
 If there is no such utility on the machine where migration process will take place, it means that you need to install the MySQL Workbench. You can download the MySQL Workbench from MySQL official website using this link: [[https://dev.mysql.com/downloads/workbench/|Download MySQL Workbench]].
-==== PostgreSQL ====
+===== PostgreSQL =====
 To perform import into PostgreSQL database in the Bin directory option we need to specify a path to the folder containing  //**psql.exe**// utility. By default this utility is located in the directory like: **c:\Program Files (x86)\PostgreSQL\[version_number]\bin\**. Otherwise, you can find it in the directory specified during the installation process of PGAdmin tool.
@@ Line 97: / Line 97: @@
 If there is no such utility on the machine where migration process will take place, it means that you need to install the PGAdmin tool. You can download it from PostgreSQL official website using this link: [[https://www.postgresql.org/ftp/pgadmin/|Download PGAdmin Tool]].
-==== EnterpriseDB ====
+===== EnterpriseDB =====
 To perform import into EnterpriseDB database in the Bin directory option we need to specify a path to the folder containing //**psql.exe**// utility. By default this utility is located in the directory like: **c:\Program Files (x86)\PostgreSQL\[version_number]\bin\**. Otherwise, you can find it in the directory specified during the installation process of PGAdmin tool.
@@ Line 103: / Line 103: @@
 If there is no such utility on the machine where migration process will take place, it means that you need to install the PGAdmin tool. You can download it from PostgreSQL official website using this link: [[https://www.postgresql.org/ftp/pgadmin/|Download PGAdmin Tool]].
-==== Greenplum ====
+===== Greenplum =====
 To perform import into Greenplum database in the Bin directory option we need to specify a path to the folder containing //**psql.exe**// utility. By default this utility is located in the directory like: **c:\Program Files (x86)\PostgreSQL\[version_number]\bin\**. Otherwise, you can find it in the directory specified during the installation process of PGAdmin tool.
@@ Line 110: / Line 110: @@
-==== Amazon Redshift ====
+===== Amazon Redshift =====
 To perform import into Redshift database in the Bin directory option we need to specify a path to the folder containing //**psql.exe**// utility. By default this utility is located in the directory like: **c:\Program Files (x86)\PostgreSQL\[version_number]\bin\**. Otherwise, you can find it in the directory specified during the installation process of PGAdmin tool.
@@ Line 117: / Line 117: @@
-==== Amazon Aurora (PostgreSQL Compatible) ====
+===== Amazon Aurora (PostgreSQL Compatible) =====
 To perform import into the Aurora database in the Bin directory option we need to specify a path to the folder containing //**psql.exe**// utility. By default this utility is located in the directory like: **c:\Program Files (x86)\PostgreSQL\[version_number]\bin\**. Otherwise, you can find it in the directory specified during the installation process of PGAdmin tool.
@@ Line 124: / Line 124: @@
-==== SAP HANA ====
+===== SAP HANA =====
 For Sap Hana database you need to specify the path to the folder on local machine that contains //**hdbsql.exe**// native utility. By default this utility is located in the directory like: **C:\\Program Files\\sap\\hdbclient\**. Otherwise, you can find it in the directory specified during the installation process of Sap Hana HDB Client.
@@ Line 130: / Line 130: @@
 If there is no such utility installed on local machine, where migration process will take place, it means that you need to install the HDB Client. If you don't have installation packages, you can download the Sap Hana HDB Client installation package from SAP HANA official website using this link: [[https://www.sap.com/developer/trials-downloads/additional-downloads/sap-hana-client-software-packages-12950.html|Download Sap Hana HDB Client]].
-==== Sybase SQL Anywhere ====
+===== Sybase SQL Anywhere =====
 For Sybase SQL Anywhere database you need to specify the path to the folder on local machine that contains //**dbisql.exe**// utility. By default this utility is located in the directory like: **c:\Program Files (x86)\Sybase\[SQL_Anywhere_Version]\win32\**. Otherwise, you can find it in the directory specified during the installation process of Sybase SQL Anywhere Client.
@@ Line 137: / Line 137: @@
-==== Sybase Adaptive Server Enterprise ====
+===== Sybase Adaptive Server Enterprise =====
 For Sybase ASE database you need to specify the path to the folder on local machine that contains //**isql.exe**// and //**bcp.exe**// utilities. By default these utilities are located in the directory like: **s:\DBClients\SybaseASE12_5\OCS-12_5\bin\**. Otherwise, you can find them in the directory specified during the installation process of Sybase PC Client or Sybase SDK.
@@ Line 144: / Line 144: @@
-==== Sybase IQ ====
+===== Sybase IQ =====
 For Sybase IQ database you need to specify the path to the folder on local machine that contains //**dbisql.exe**// utility. By default this utility is located in the directory like: **C:\sybaseIQ\[DB_Version]\Bin64\**. Otherwise, you can find it in the directory specified during the installation process of Sap IQ Client Software.
@@ Line 151: / Line 151: @@
-==== Teradata ====
+===== Teradata =====
 For Teradata database you need to specify the path to the folder containing //**bteq.exe**// and //**fastload.exe**// native utilities. By default these utilities are located in the directory like: **c:\Program Files (x86)\Teradata\Client\15.00\bin\**. Otherwise, you can find it in the directory specified during the installation process of Teradata Tools and Utilities package.