We are happy to announce that latest version of Advanced ETL Processor supports creation of Tableau Hyper files

What’s Hyper?

Under the hood, Hyper is the technology that now powers Tableau’s data engine. The data engine is what handles opening, creating, refreshing, and querying your extracts.

https://www.tableau.com/about/blog/2018/1/extracts-hyper-speed-what-you-need-know-79397

Full list of chages:

  • Added:  Support fot Hyper Tableau files (64 bit version)
  • Added:  Upload type option to Publish Tableau File action dialogue
  • Added:  "If File Exists" option to Publish Tableau File action dialogue.
  • Added:  Support for hyper,tdsx,twb,twbx files to Publish Tableau File action
  • Improved : Publish Tableau File action uses rest now
  • Improved: Third party components update

About Tableau:

Tableau is business intelligence software that allows anyone to connect to data in a few clicks, then visualize and create interactive, shareable dashboards with a few more. It's easy enough that any Excel user can learn it, but powerful enough to satisfy even the most complex analytical problems. Securely sharing your findings with others only takes seconds.

The result is BI software that you can trust to actually deliver answers to the people that need them.

http://www.tableausoftware.com/business-intelligence

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 life everyone easier 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
  • Management console can be used make repository backups now
  • Repository connection details and  designer user interface settings are no longer stored in the registry text files are used instead
  • 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 imrovments
More information:

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

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

Note: List of variables is shared between all applications

Connections.ini holds list of all available repository connections

Note: This list is shared between all applications

DesktopConnection.ini this file holds designer repository connection name

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

Upgrade procedure (from VI version 9 and AETL version 6):

  1. Create repository backup.
  2. Stop all services
  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 brand new repository and connect to it
  6. Restore repository from backup
  7. Run the following SQL against 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

We have 250 guests and no members online