New versions of Visual Importer ETL and Advanced ETL Processor are available for download

The most important change is how settings are stored.  All of them used to be saved in the registry key HKEY_LOCAL_MACHINE and since Microsoft had tightened windows security it brought a lot of problems and error messages.  In order to make the life of everyone easier, the decision was made to move common settings into "ini files" and user-specific settings to HKEY_CURRENT_USER  registry key. The benefit of storing common settings in ini files that it is extremely easy to copy repository settings from one computer to another.  

Other changes are:
  • Support for MongoDB was introduced
  • The management console can be used to make repository backups now
  • Repository connection details and  designer user interface settings are no longer stored in the registry text files are used instead
  • The management console can be used to create repository backups
  • Advanced ETL Processor Services - XXX were renamed to ETL Server - XXX
  • Ability to delete nodes was introduced
  • Added Execution Timeout
  • Various Bug fixes and improvements
More information:

All settings are stored in C:\ProgramData\ETL-Tools.com folder, which makes moving software to the different computer much easier.

Options.ini holds designer user interface settings plus global variables values

Note: The List of variables is shared between all applications

Connections.ini holds the list of all available repository connections

Note: This list is shared between all applications

DesktopConnection.ini this file holds the designer repository connection name

ServerConnection.ini this file holds execution agent, management console and monitors repository connection name

Upgrade procedure (from VI versions 9 and AETL version 6):
  1. Create repository backup.
  2. Stop all services(Enterprise version only)
  3. Uninstall software
  4. Upgrade repository
  5. Install software
Repository Upgrade Procedure:

Run the following SQL against your repository:

All repository types

Insert into OBJECT_TYPES
(OBJECT_TYPE,OBJECT_TYPE_NAME)
Values
('903','MongoDB Connection')

Insert into OBJECT_TYPES
(OBJECT_TYPE,OBJECT_TYPE_NAME)
Values
('904','MongoDB Connections')

INSERT INTO OBJECTS_TREE
(OBJECT_ID,
PARENT_ID,
NAME,
OBJECT_TYPE
)
Select
OBJECT_ID*-4 as OBJECT_ID,
PARENT_ID,
'MongoDB' as NAME,
903 as OBJECT_TYPE
From
OBJECTS_TREE
where OBJECTS_TREE.OBJECT_TYPE=320

UPDATE OBJECT_TYPES
set OBJECT_TYPE_GROUP=22000
WHERE OBJECT_TYPE= '903'

For Oracle

ALTER TABLE QUEUE ADD TERMINATE_ON_TIMEOUT NUMBER (1) default 0 NOT NULL
ALTER TABLE QUEUE_HISTORY ADD TERMINATE_ON_TIMEOUT NUMBER (1) default 0 NOT NULL
ALTER TABLE SCHEDULE ADD TERMINATE_ON_TIMEOUT NUMBER (1) default 0 NOT NULL
ALTER TABLE EVENT_MONITORS ADD TERMINATE_ON_TIMEOUT NUMBER (1) default 0 NOT NULL

For MS SQL Server

ALTER TABLE QUEUE ADD TERMINATE_ON_TIMEOUT decimal(1, 0) NULL default 0
ALTER TABLE QUEUE_HISTORY ADD TERMINATE_ON_TIMEOUT decimal(1, 0) NULL default 0
ALTER TABLE SCHEDULE ADD TERMINATE_ON_TIMEOUT decimal(1, 0) NULL default 0
ALTER TABLE EVENT_MONITORS ADD TERMINATE_ON_TIMEOUT decimal(1, 0) NULL default 0

For MySQL

ALTER TABLE QUEUE ADD TERMINATE_ON_TIMEOUT NUMERIC(1) DEFAULT 0
ALTER TABLE QUEUE_HISTORY ADD TERMINATE_ON_TIMEOUT NUMERIC(1) DEFAULT 0
ALTER TABLE SCHEDULE ADD TERMINATE_ON_TIMEOUT NUMERIC(1) DEFAULT 0
ALTER TABLE EVENT_MONITORS ADD TERMINATE_ON_TIMEOUT NUMERIC(1) DEFAULT 0

For PostgreSQL

ALTER TABLE QUEUE ADD TERMINATE_ON_TIMEOUT NUMERIC(1) DEFAULT 0
ALTER TABLE QUEUE_HISTORY ADD TERMINATE_ON_TIMEOUT NUMERIC(1) DEFAULT 0
ALTER TABLE SCHEDULE ADD TERMINATE_ON_TIMEOUT NUMERIC(1) DEFAULT 0
ALTER TABLE EVENT_MONITORS ADD TERMINATE_ON_TIMEOUT NUMERIC(1) DEFAULT 0

For Interbase

ALTER TABLE QUEUE ADD TERMINATE_ON_TIMEOUT NUMERIC (1) default 0,
ALTER TABLE QUEUE_HISTORY ADD TERMINATE_ON_TIMEOUT NUMERIC(1) DEFAULT 0
ALTER TABLE SCHEDULE ADD TERMINATE_ON_TIMEOUT NUMERIC(1) DEFAULT 0
ALTER TABLE EVENT_MONITORS ADD TERMINATE_ON_TIMEOUT NUMERIC(1) DEFAULT 0

Upgrade procedure (from VI version 8 and AETL version 5):
  1. Create repository backup (backup must have one file inside).
  2. Stop all services
  3. Uninstall software
  4. Install software
  5. Create a brand new repository and connect to it
  6. Restore repository from backup
  7. Run the following SQL against the repository:

INSERT INTO OBJECTS_TREE
(OBJECT_ID,
PARENT_ID,
NAME,
OBJECT_TYPE
)
Select
OBJECT_ID*-4 as OBJECT_ID,
PARENT_ID,
'MongoDB' as NAME,
903 as OBJECT_TYPE
From
OBJECTS_TREE
where OBJECTS_TREE.OBJECT_TYPE=320

UPDATE OBJECT_TYPES
set OBJECT_TYPE_GROUP=22000
WHERE OBJECT_TYPE= '903'

Note: If you are having problems upgrading our software please let us know and we will do our best to assist you

Download Free Trial of Advanced ETL Processor
Direct link, no registration required.