Ispirer Ispirer
 


Ispirer Home Page Request SQLWays

Utilities That Are Used To Make Import In MnMTK

When migrating from one database into another database using the SQLWays Wizard tool, there is a possibility to execute the import process automatically. To do that you need to know about the utilities that will be used to execute an import process.

SQLWays Wizard generates the .bat script for each converted object. And in this script you can find a command to the utility that will be use to perform an import process. And during the import process tool just run this command to the native utility and then, utility by itself connects to the target database and tries to execute the converted sql code in the target database.

For each target database SQLWays generates commands to the different native utilities. Also note that SQLWays doesn't use any third-part tools or utilities to make an import. It generates commands only for 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 located on the “Specify Import Options” page in the SQLWays Wizard Tool:


Below you can find the information about the databases, its native utilities that will be used by the SQLWays tool and where to find them.

Databases and Utilities

Oracle

For making an import into the Oracle database in the Bin directory Option we need to specify a path to the folder containing the sqlldr.exe and the sqlplus.exe utilities. By default this utilities will be located in the directory like: c:\app\[user_name]\product\[DB_Version]\client_1\BIN\. Or on another directory, if it was changed during the installation process of Oracle database.

If there is 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 the official Oracle site using this link: 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.

Ispirer Note:
To be able to make an import into Oracle you will have to tune the TNS service name and provide this name on the “Choose a Target Database” page in SQLWays Wizard tool. How to tune the TNS name you can find in the article: How to Tune the TNS Service Name For Oracle

Microsoft SQL Server

For Microsoft SQL Server you need to specify a path to the folder containing the bcp.exe and sqlcmd.exe native utilities. By default this utilities will be located in the directory like: c:\Program Files\Microsoft SQL Server\[DB_Version]\Tools\Binn\. Or on another directory, if it was changed during the installation process of Microsoft SQL Server database. Or you can check the whether these utilities located in the Management Studio installation directory.

If there is 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 the official Microsoft site using this link: Download SQL Server Client.

Azure SQL Data Warehouse

For Microsoft SQL Data Warehouse you need to specify a path to the folder containing the bcp.exe and sqlcmd.exe native utilities. By default this utilities will be located in the directory like: c:\Program Files\Microsoft SQL Server\[DB_Version]\Tools\Binn\. Or on another directory, if it was changed during the installation process of Microsoft SQL Server database. Or you can check the whether these utilities located in the Management Studio installation directory.

If there is 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 the official Microsoft site using this link: Download SQL Server Client.

Azure SQL Database

For Microsoft Azure SQL Database you need to specify a path to the folder containing the bcp.exe and sqlcmd.exe native utilities. By default this utilities will be located in the directory like: c:\Program Files\Microsoft SQL Server\[DB_Version]\Tools\Binn\. Or on another directory, if it was changed during the installation process of Microsoft SQL Server database. Or you can check the whether these utilities located in the Management Studio installation directory.

If there is 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 the official Microsoft site using this link: Download SQL Server Client.

IBM DB2

For IBM DB2 database you need to specify a path to the folder containing the db2.exe native utility. By default this utility will be located in the directory like: c:\Program Files (x86)\IBM\SQLLIB\BIN\. Or on another directory, if it was changed 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 the official IBM site: https://www.ibm.com.

IBM Informix

For Informix database you need to specify a path to the folder containing the dbaccess.exe native utility. By default this utility will be located in the directory like: c:\Program Files (x86)\Informix Client-SDK\bin\. Or on another directory, if it was changed 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 the official IBM site: https://www.ibm.com.

IBM Netezza

For Netezza database you need to specify a path to the folder containing the nzsql.exe native utility. By default this utility will be located in the directory like: C:\\Program Files (x86)\\IBM Netezza Tools\\Bin\. Or on another directory, if it was changed 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 the official IBM site: https://www.ibm.com.

MySQL

For MySQL database you need to specify a path to the folder containing the mysql.exe native utility. By default this utilities will be located in the directory like: c:\Program Files (x86)\MySQL\MySQL Workbench 6.1 CE\. Or on another directory, if it was changed during the installation process of MySQL database.

If there is no such utilities 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 the official MySQL site using this link: Download MySQL Workbench.

MariaDB

For MariaDB database you need to specify a path to the folder containing the mysql.exe native utility. By default this utilities will be located in the directory like: c:\Program Files (x86)\MySQL\MySQL Workbench 6.1 CE\. Or on another directory, if it was changed during the installation process of MySQL Workbench.

If there is no such utilities 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 the official MySQL site using this link: Download MySQL Workbench.

Amazon Aurora (MySQL Compatible)

For Amazon Aurora database you need to specify a path to the folder containing the mysql.exe native utility. By default this utilities will be located in the directory like: c:\Program Files (x86)\MySQL\MySQL Workbench 6.1 CE\. Or on another directory, if it was changed during the installation process of MySQL Workbench.

If there is no such utilities 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 the official MySQL site using this link: Download MySQL Workbench.

PostgreSQL

For making an import into the PostgreSQL database in the Bin directory option we need to specify a path to the folder containing the psql.exe utility. By default this utility will be located in the directory like: c:\Program Files (x86)\PostgreSQL\[version_number]\bin\. Or on another directory, if it was changed 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 the official PostgreSQL site using this link: Download PGAdmin Tool.

EnterpriseDB

For making an import into the EnterpriseDB database in the Bin directory option we need to specify a path to the folder containing the psql.exe utility. By default this utility will be located in the directory like: c:\Program Files (x86)\PostgreSQL\[version_number]\bin\. Or on another directory, if it was changed 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 the official PostgreSQL site using this link: Download PGAdmin Tool.

Greenplum

For making an import into the Greenplum database in the Bin directory option we need to specify a path to the folder containing the psql.exe utility. By default this utility will be located in the directory like: c:\Program Files (x86)\PostgreSQL\[version_number]\bin\. Or on another directory, if it was changed 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 the official PostgreSQL site using this link: Download PGAdmin Tool.

Amazon Redshift

For making an import into the Redshift database in the Bin directory option we need to specify a path to the folder containing the psql.exe utility. By default this utility will be located in the directory like: c:\Program Files (x86)\PostgreSQL\[version_number]\bin\. Or on another directory, if it was changed 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 the official PostgreSQL site using this link: Download PGAdmin Tool.

Amazon Aurora (PostgreSQL Compatible)

For making an import into the Aurora database in the Bin directory option we need to specify a path to the folder containing the psql.exe utility. By default this utility will be located in the directory like: c:\Program Files (x86)\PostgreSQL\[version_number]\bin\. Or on another directory, if it was changed 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 the official PostgreSQL site using this link: Download PGAdmin Tool.

SAP HANA

For Sap Hana database you need to specify the path to the folder on local machine that contains the hdbsql.exe native utility. By default this utility will be located in the directory like: C:\\Program Files\\sap\\hdbclient\. Or on another directory, if it was changed during the installation 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, then you can download the Sap Hana HDB Client installation package from the official Sap Hana site using this link: Download Sap Hana HDB Client.

Sybase SQL Anywhere

For Sybase SQL Anywhere database you need to specify the path to the folder on local machine that contains the dbisql.exe utility. By default this utility will be located in the directory like: c:\Program Files (x86)\Sybase\[SQL_Anywhere_Version]\win32\. Or on another directory, if it was changed during the installation 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, then you can download the required installation package from the Sap official site using this link: Download Sybase SQL Anywhere Client.

Sybase Adaptive Server Enterprise

For Sybase ASE database you need to specify the path to the folder on local machine that contains the isql.exe and bcp.exe utilities. By default these utilities will be located in the directory like: s:\DBClients\SybaseASE12_5\OCS-12_5\bin\. Or on another directory, if it was changed during the installation of Sybase PC Client or Sybase SDK.

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 PC Client or SDK for Sybase for latest versions. If you don't have installation packages, then you can download the required installation package from the Sap Software Download Center using this link: Sap Software Download Center.

Sybase IQ

For Sybase IQ database you need to specify the path to the folder on local machine that contains the dbisql.exe utility. By default this utility will be located in the directory like: C:\sybaseIQ\[DB_Version]\Bin64\. Or on another directory, if it was changed during the installation 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, then you can download the required installation package from the Sap Software Download Center using this link: Sap Software Download Center.

Teradata

For Teradata database you need to specify the path to the folder containing the bteq.exe and fastload.exe native utility. By default this utility will be located in the directory like: c:\Program Files (x86)\Teradata\Client\15.00\bin\. Or on another directory, if it was changed during the installation of Teradata Tools and Utilities package.

If there is no such utilities installed on local machine, where migration process will take place, it means that you need to install these utilities. If you don't have installation packages for bteq.exe and fastload.exe, then you can download the TTU (Teradata Tools and Utilities) package from the official Teradata site using this link: Download Teradata Tools and Utilities Package. You need to open this archive and run the installation of only the required utilities.


Ispirer Home Page Request SQLWays

sqlways/faq/utilities-to-make-import.txt · Last modified: November 06, 2018, 10:40:18 AM by alexandr.kirpichny
 
© 1999-2019, Ispirer Systems Ltd.
All Rights Reserved.  Privacy Statement