EMS Data Import version 2.2 and Data Export version 2.3 are now available!

Posted on 2006-11-08

EMS Data Import 2.2 and Data Export 2.3 are now available and can be downloaded from the download pages:

Data Export for PostgreSQL http://www.sqlmanager.net/products/postgresql/dataexport/download

Data Import for PostgreSQL http://www.sqlmanager.net/products/postgresql/dataimport/download

What’s new in Data Export version 2.3

  • The amount of memory consumed is significantly decreased when exporting large files.

  • Now the databases in lists are sorted.

  • When truncating source field names the fields with identical names could appear in DBF file. Fixed now.

  • The ability to set the Connection Timeout parameter added. (MS SQL Server)

  • Now it’s possible to tune the performance via the Cursor Location option. (MS SQL Server)

  • The "login failed" message used to appear if the database name contained the ‘.’ (dot) symbol. Fixed now. (MS SQL Server)

  • Some small improvements and bug fixes.

What’s new in Data Import version 2.2

  • The ability to import data from VisualFoxPro DBF format added.

  • The amount of memory consumed is significantly decreased when importing large files.

  • When importing data from XLS format a shift of data from lower cells into upper ones occurred if the upper cells were empty. Fixed now.

  • Import from file containing the ‘.’ (dot) symbol in its name was not possible. Fixed now.

  • When importing data from CSV files in some rare cases the duplication of data contained in some columns occurred. Fixed now.

  • Fields of MEMO type with a single end-of-section marker (#26) symbol used to be read incorrectly when importing data from DBT files (DBF format). Fixed now.

  • A wrong result script used to be generated when using import operations like Update, Update or Insert, Delete, Delete or Insert. Fixed now.

  • The ability to set Connection Timeout parameter added. (MS SQL Server)

  • Now it’s possible to tune the performance via the Cursor Location option. (MS SQL Server)

  • Some small improvements and bug fixes.

We hope you'll enjoy working with our products!

This post has been migrated from a previous version of the PostgreSQL website. We apologise for any formatting issues caused by the migration.