Differences

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

--- faq:migration-toolkit:utilities-to-make-import [2019/06/26 10:03]
vladimir.gribok
+++ faq:migration-toolkit:utilities-to-make-import [2019/09/20 12:20]
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?800|}}
@@ Line 19: / Line 19: @@
 ===== 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.
+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 the Oracle database.
-If there are no such utilities on the machine where migration process will take place, it means that you need to install the Oracle Client. You can download the Oracle client from Oracle official website using this link: [[https://www.oracle.com/technetwork/database/database-technologies/instant-client/downloads/index.html|Download Oracle Client]].
+If there are no such utilities on the machine where migration process is performed, you need to install Oracle Client. You can download the Oracle client from Oracle official website using this link: [[https://www.oracle.com/technetwork/database/database-technologies/instant-client/downloads/index.html|Download Oracle Client]].
 Please note that you need to choose "Administrator" installation type of the client to get all the required utilities installed on your machine.
@@ Line 32: / Line 32: @@
 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.
-If there are no such utilities on the machine where migration process will take place, it means that you need to install the Microsoft SQL Server Client. You can download it from Microsoft official website using this link: [[https://www.microsoft.com/en-us/download/details.aspx?id=50402|Download SQL Server Client]].
+If there are no such utilities on the machine where migration process is performed, you need to install Microsoft SQL Server Client. You can download it from Microsoft official website using this link: [[https://www.microsoft.com/en-us/download/details.aspx?id=50402|Download SQL Server Client]].
 ===== 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.
+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 the database. You can also check the location of these utilities in Management Studio installation directory.
-If there are no such utilities on the machine where migration process will take place, it means that you need to install the Microsoft SQL Server Client. You can download the SQL Server client from Microsoft official website using this link: [[https://www.microsoft.com/en-us/download/details.aspx?id=50402|Download SQL Server Client]].
+If there are no such utilities on the machine where migration process is performed, you need to install Microsoft SQL Server Client. You can download SQL Server client from Microsoft official website using this link: [[https://www.microsoft.com/en-us/download/details.aspx?id=50402|Download SQL Server Client]].
 ==== 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.
+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 the database. You can also check the location of these utilities in Management Studio installation directory.
-If there are no such utilities on the machine where migration process will take place, it means that you need to install the Microsoft SQL Server Client. You can download the SQLServer client from Microsoft official website using this link: [[https://www.microsoft.com/en-us/download/details.aspx?id=50402|Download SQL Server Client]].
+If there are no such utilities on the machine where migration process is performed, you need to install Microsoft SQL Server Client. You can download SQL Server client from Microsoft official website using this link: [[https://www.microsoft.com/en-us/download/details.aspx?id=50402|Download SQL Server Client]].
@@ Line 53: / Line 53: @@
 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.
-If there is no such utility on the machine where migration process will take place, it means that you need to install the DB2 Data Server Client. You can download it from IBM official website: [[https://www.ibm.com]].
+If there is no such utility on the machine where migration process is performed, you need to install DB2 Data Server Client. You can download it from IBM official website: [[https://www.ibm.com]].
@@ Line 61: / Line 61: @@
 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.
-If there is no such utility on the machine where migration process will take place, it means that you need to install the Informix SDK Client. You can download it from IBM official website: [[https://www.ibm.com]].
+If there is no such utility on the machine where migration process is performed, you need to install Informix SDK Client. You can download it from IBM official website: [[https://www.ibm.com]].
@@ Line 68: / Line 68: @@
 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.
-If there is no such utility on the machine where migration process will take place, it means that you need to install the IBM Netezza Client. You can download it from IBM official website: [[https://www.ibm.com]].
+If there is no such utility on the machine where migration process is performed, you need to install IBM Netezza Client. You can download it from IBM official website: [[https://www.ibm.com]].
@@ Line 75: / Line 75: @@
 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.
-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]].
+If there is no such utility on the machine where migration process is performed, you need to install MySQL Workbench. You can download MySQL Workbench from MySQL official website using this link: [[https://dev.mysql.com/downloads/workbench/|Download MySQL Workbench]].
@@ Line 82: / Line 82: @@
 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.
-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]].
+If there is no such utility on the machine where migration process is performed, you need to install MySQL Workbench. You can download MySQL Workbench from MySQL official website using this link: [[https://dev.mysql.com/downloads/workbench/|Download MySQL Workbench]].
@@ Line 89: / Line 89: @@
 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.
-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]].
+If there is no such utility on the machine where migration process is performed, you need to install MySQL Workbench. You can download MySQL Workbench from MySQL official website using this link: [[https://dev.mysql.com/downloads/workbench/|Download MySQL Workbench]].
 ===== PostgreSQL =====
@@ Line 95: / Line 95: @@
 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.
-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]].
+If there is no such utility on the machine where migration process is performed, you need to install PGAdmin tool. You can download it from PostgreSQL official website using this link: [[https://www.postgresql.org/ftp/pgadmin/|Download PGAdmin Tool]].
 ===== EnterpriseDB =====
@@ Line 101: / Line 101: @@
 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.
-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]].
+If there is no such utility on the machine where migration process is performed, you need to install PGAdmin tool. You can download it from PostgreSQL official website using this link: [[https://www.postgresql.org/ftp/pgadmin/|Download PGAdmin Tool]].
 ===== Greenplum =====
@@ Line 107: / Line 107: @@
 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.
-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]].
+If there is no such utility on the machine where migration process is performed, 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]].
@@ Line 114: / Line 114: @@
 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.
-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]].
+If there is no such utility on the machine where migration process is performed, you need to install PGAdmin tool. You can download it from PostgreSQL official website using this link: [[https://www.postgresql.org/ftp/pgadmin/|Download PGAdmin Tool]].
@@ Line 121: / Line 121: @@
 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.
-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]].
+If there is no such utility on the machine where migration process is performed, you need to install PGAdmin tool. You can download it from PostgreSQL official website using this link: [[https://www.postgresql.org/ftp/pgadmin/|Download PGAdmin Tool]].
@@ Line 128: / Line 128: @@
 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.
-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]].
+If there is no such utility installed on local machine, where migration process is performed, you need to install HDB Client. If you don't have installation packages, you can download  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 =====
@@ Line 134: / Line 134: @@
 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.
-If there is no such utility installed on local machine, where migration process will take place, it means that you need to install the Sybase SQL Anywhere Client. If you don't have installation packages, you can download the required installation package from SAP official site using this link: [[https://archive.sap.com/documents/docs/DOC-35857|Download Sybase SQL Anywhere Client]].
+If there is no such utility installed on local machine where migration process is performed, you need to install Sybase SQL Anywhere Client. If you don't have installation packages, you can download the required installation package from SAP official site using this link: [[https://archive.sap.com/documents/docs/DOC-35857|Download Sybase SQL Anywhere Client]].
@@ Line 141: / Line 141: @@
 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.
-If there are no such utilities installed on local machine, where migration process will take place, it means that you need to install the Sybase PC Client or SDK for Sybase for latest versions. If you don't have installation packages, you can download the required installation package from the Sap Software Download Center using this link: [[http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/softwarecenter|Sap Software Download Center]].
+If there are no such utilities installed on local machine where migration process is performed, you need to install Sybase PC Client or SDK for Sybase for latest versions. If you don't have installation packages, you can download the required installation package from the Sap Software Download Center using this link: [[http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/softwarecenter|Sap Software Download Center]].
@@ Line 148: / Line 148: @@
 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.
-If there is no such utility installed on local machine, where migration process will take place, it means that you need to install the Sap IQ Client Software. If you don't have installation packages, you can download the required installation package from Sap Software Download Center using this link: [[http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/softwarecenter|Sap Software Download Center]].
+If there is no such utility installed on local machine, where migration process is performed, you need to install Sap IQ Client Software. If you don't have installation packages, you can download the required installation package from Sap Software Download Center using this link: [[http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/softwarecenter|Sap Software Download Center]].
@@ Line 155: / Line 155: @@
 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.
-If there are no such utilities installed on local machine, where migration process will take place, it means that you need to install them. If you don't have installation packages for //**bteq.exe**// and //**fastload.exe**//, you can download the TTU (Teradata Tools and Utilities) package from Teradata official website using this link: [[https://downloads.teradata.com/download/tools/teradata-tools-and-utilities-windows-installation-package|Download Teradata Tools and Utilities Package]]. You need to open this archive and run the installation of the required utilities only.
+If there are no such utilities installed on local machine where migration process will take place, you need to install them. If you don't have installation packages for //**bteq.exe**// and //**fastload.exe**//, you can download the TTU (Teradata Tools and Utilities) package from Teradata official website using this link: [[https://downloads.teradata.com/download/tools/teradata-tools-and-utilities-windows-installation-package|Download Teradata Tools and Utilities Package]]. You need to open this archive and run the installation of the required utilities only.