You can export data directly to your target database using Exportizer Pro or Exportizer Enterprise. But anyway, if you have a third party SQL tool which can execute the script in the target database, you can export the data to a SQL script, which is the intermediate layer between your source and target databases.
Please note, that when choosing exporting to SQL, you do the things twice: first, export the data to SQL script; second, load data from the script to your destination database. Therefore, this option can be less effective, especially for large datasets or when automating the data exporting.
To export from dBase to SQL script, please consider the following:
- Exportizer standard edition is enough to perform the task
- You can work with dBase data either via ADO or BDE interface, but note:
- When using ADO and ODBC, the Exportizer bitness must match the bitness of the corresponding ODBC driver
- When using ADO and Microsoft Jet, Exportizer 32-bit must be used
- When using ADO and Microsoft ACE, the Exportizer bitness must match the bitness of the installed Microsoft Office
- When using BDE, Exportizer 32-bit must be used
Configuring DBF to SQL Script Exporting
- Launch Exportizer.
- Register your source dBase database. It must be a folder with .dbf files. Interface can be ADO or BDE. In the latter case, you'll probably need some preparations on Windows Vista+ to get it to work. In case of ADO, you can use your own connection string (see examples) to connect the database instead of specifying just the folder name. To let you easily identify the database, give it a friendly name.
- Open the registered dBase database.
- Chose a table to export.
- Click Export button.
- Go to the SQL Script tab and specify a destination SQL file.
- Specify the export parameters: target table name, SQL statement type, target database type, file encoding and so on.
- Click Next and check the source-to-target field mappings.
- Click Export.