Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Click here for instructions to upgrade your ETL+.

...

Expand
titleDownload, Release Notes, Release Date

Warning: This beta version is NOT recommended for production installations yet.

Download Links:
- ETL+ 64 bits: DataSelf ETL Plus - Beta 2022.06.2102.exe (5MB)
- ETL+ 32 bits: DataSelf ETL Plus 32bits - Beta 2022.06.2102.exe (5MB)
- DataSelf Agent: DataSelf Agent.exe (60KB)
Released: 06/21/2022 (beta release #9)

New Features

  1. ETL page, left panel renamed to “ETL Source”.

  2. ETL Page, center panel: Renamed Data Warehouse to ETL Objects. More descriptive of what the panel is about. Objects currently include source headings (to group sources' tables together), SQL schemas, tables, and table columns.

  3. ETL Page: Renaming tables on the center panel renames the physical data warehouse tables.

  4. ETL Page: Duplicating tables on the center panel duplicates the physical data warehouse tables. This is helpful when users want to perform tests on a table without affecting the official one.

  5. ETL Page: Deleting tables on the center panel deletes the physical data warehouse tables. User is prompted to confirm the physical deletion.

  6. ETL Page: Deleting ETL+ Sources deletes its mapped tables on the center panel and now also the physical data warehouse tables. User is prompted to confirm the physical table deletion.

  7. ETL page, title now shows the connected “Data Warehouse: [<SqlServerName>].[<Database>]”

  8. ETL Page, ETL Objects: zData Warehouse heading renamed to zData Warehouse (Reimports). More descriptive of the tables under this header.

  9. ETL page, left pane shortcut: select a source → (Ctrl + i) opens its Properties.

  10. ETL page, left pane shortcut: double-click a table to add/map it to the load process.

  11. ETL page, left pane shortcut: (F5) to refresh a source.

  12. ETL page: Job icon updated.

  13. ETL page: Settings icon updated.

  14. ETL Page: Find feature to quickly highlight matches on sources, data warehouse tables, and SQL Statements.

  15. ETL Page: Click the Find icon to expose/collapse the search box

  16. ETL page, center pane shortcut: select a table → (Ctrl + Del) key to delete.

  17. ETL page, center pane shortcut: select a table → (Ctrl + 2) key to duplicate.

  18. ETL page, center pane shortcut: select a table → (F2) key to rename.

  19. ETL page, center pane shortcut: select a table → (Ctrl + D) key to open Design.

  20. ETL page, center pane shortcut: select a table → (Ctrl + O) key to load its Columns.

  21. ETL page, center pane shortcut: select a table → (Ctrl + P) key to preview.

  22. ETL page, center pane shortcut: select a table → (Ctrl + L) key to Load Now.

  23. ETL page, center pane: Added ... icon to the panel header for additional non-popular actions.

  24. ETL page, center pane: select a table → ... → Show Columns.

  25. ETL page, center pane: select a table → ... → Load All Columns.

  26. ETL page, center pane: select a table → ... → Expand/Collapse All source groups.

  27. ETL page, center pane: select a table → ... → Download to CSV.

  28. ETL page shortcut: click (F1) key to open Help.

  29. ETL page shortcut: click (Ctrl + F) to go to the Find box.

  30. ETL page shortcut: click (Ctrl + G) to open the Log page.

  31. ETL page shortcut: click (Ctrl + J) to open the Job page.

  32. ETL page shortcut: click (Ctrl + S) to Save.

  33. ETL page shortcut: click (Ctrl + O) inside of ETL SQL Statement to Confirm.

  34. ETL Page: Right-click a data warehouse table → Download to CSV downloads the data in CSV format into ETL+ folder/DS_Downloads/<TableName>.csv.

  35. Job: “Refresh Batch” renamed to “Job” - this feature can run scripts that are not “refreshes”.

  36. DataSelf Agent: Greatly anticipated ETL+ auxiliary application to execute scheduled and remote tasks. Long-term vision: a user runs ETL+ on her laptop at a hotel and requests a data refresh from her on-premises ETL+ install, and orders a margarita (drink orders not included in ETL+ lol). Their on-prem DS Agent receives and executes the request on the on-prem ETL+. And then it notifies the user when the refresh is complete. Magic happens while the margarita buzz kicks in!

  37. Agent: Introduces the concept of ETL+ Production installs where the locally deployed Agent runs scheduled jobs and remote tasks.

  38. Agent: An ETL+ Job can be associated to one Agent to run it on schedule or on-demand, or via WTS.

  39. Agent: ETL+ Production installs must have direct access to source systems and have the Agent locally deployed and running with a local Windows Admin user.

  40. Agent: ETL+ will capture in the metadata the Windows Device name to associate the ETL+ Entity and Job IDs to run by the Agent.

  41. Agent: When assigning a computer to run the Agent for the first time, ETL+ assigns the username and password saved on the Job → Properties → Agent credentials. This user must have local Windows Admin Rights.

  42. Agent: When assigning a computer to run the Agent for the first time, ETL+ creates an WTS task to automatically run the Agent when restarting the computer.

  43. Agent: Runs as a Windows service (in the background) and checks the cloud metadata every 10 secs for instructions to execute.

  44. Agent: Checks the cloud metadata if there are Jobs to run now. The rule is: (Jobs associated to run by this Agent) & Enabled & (Next Run Time <= now).

  45. Agent: Checks the cloud metadata if there are on-demand tasks to execute. Currently, it can execute two tasks remotely: run a Job now, and kill the execution of a running Job.

  46. Agent: DateTime values related to the Agent are fixed in PST. Next release will add flexibility to this setting.

  47. Agent Protocol: The communication between the Agent and the cloud is via a single metadata table.

  48. Agent Protocol: The Agent and ETL+ use the metadata table to monitor actions such as terminate a running Job.

  49. Job: Added Status column on the job list to show which app runs the schedule of a job. Options: WTS (Windows Task Scheduler) and DataSelf Agent.

  50. Job: Status column showing WTS: The job runs via Windows Task Scheduler. ETL+ currently can only create and overwrite WTS tasks via the Schedule button.

  51. Job: Status column showing the Agent status: Ready, Disable, Running, Stopping.

  52. Job - Icons: Added Run Job via Agent. This sends a message to the Agent to run the Job on demand.

  53. Job - Icons: Added ... (More Actions).

  54. Job - Icons: Added End Job via Agent icon under the ... icon.

  55. Job - Icons: Added Enable icon under the ... icon.

  56. Job - Icons: Added Disable icon under the ... icon.

  57. Job - Icons: Moved Rename Job icon under the ... icon.

  58. Job - Icons: Moved Delete Job icon under the ... icon.

  59. Job - Right-click: Same changes as Job - Icons above.

  60. Job: Agent column showing Agent Ready: This means the Agent will run that job on its schedule.

  61. Job: Agent column showing Agent Disabled: This means the Agent will not run that job on its schedule.

  62. Job: Agent column showing Agent Running: This happens after a user triggers an on-demand Run Job via Agent. Currently, this Running status won’t know when the Job is completed. Users can monitor the Job running status via the Log or by the refresh email.

  63. Job: Agent column showing Agent Stopping: This happens after a user triggers an on-demand End Job via Agent. Currently, this Stopping status won’t know when the Job ends. Users can monitor the Job running status via the Log.

  64. Job - Pop up: Shows Job name

  65. Job - Pop up: Shows Agent to run the Job. Computer Name if DataSelf Agent will run the Job.

  66. Job - Pop up: Shows Job Schedule.

  67. Job - Pop up: Shows Load Type.

  68. Job - Pop up: Shows Last Run Time.

  69. Job - Pop up: Shows Next Run Time.

  70. Job: Removed Windows Task Scheduler (WTS) section.

  71. Job: Removed WTS Settings.

  72. Job: Added Properties icon which shows a section for Schedule, Load Type, and Agent.

  73. Job - Schedule: Added radio buttons to set which engine runs schedules: WTS or DataSelf Agent.

  74. Job - Schedule: When radio button = WTS, the feature works like in prior ETL+ releases.

  75. Job - Schedule: When radio button = DataSelf Agent, the Agent will be responsible for running the Job’s schedule.

  76. Job - Agent: Press the Apply button to associate a Job to run on this computer.

  77. Job: Added icon to open the Log page.

  78. Design: When changing the Data Type of a column, ETL+ posts the SQL expressions automatically applied. Users can edit the expression.

  79. Design: After a SQL expression is posted to a column, if a user changes the column’s Data Type again, ETL+ will prompt if it should update the SQL expression.

  80. Design: Loading of MS SQL Timestamp columns automatically converted to char(23).

  81. Load Engine: Depending on the source system, loading of Date and DateTime columns automatically converts invalid values to NULL.

  82. Load Engine: The delta filter column now creates a physical index in the data warehouse.

  83. Load Engine: PK columns used in delta loads now create physical indexes in the data warehouse.

  84. Load Engine: Adjustments when recalculating MS SQL indexes for the filter column used in tables with Replace. Resulting in significant performance improvement when processing deltas in large tables.

  85. Load Engine: Adjustments when recalculating MS SQL indexes for the filter and PK columns used in tables with Upsert. Resulting in significant performance improvement when processing deltas in large tables.

  86. Load Engine: If an ETL+ entity tries to load a table that is currently being loaded by another entity, it’ll show the message “Another ETL+ is loading this table. Waiting for table release.”

  87. Load Engine: If an ETL+ entity tries to load a table that is currently being loaded by another entity, every 15 secs it’ll show the message “Checking table release…”

  88. Load Engine: If an ETL+ entity tries to load a table that is currently being loaded by another entity, but the other entity isn’t active for over 90 seconds, the new entity takes over the table load.

  89. Load Engine: Checking if Log tables exist only during the opening of an entity (instead of during the load of every table).

  90. Load Engine: Added MS Access as a new source type.

  91. Load Engine - MS Access: Enter file path and password if required.

  92. Load Engine: Added PostgreSQL as a new source type.

  93. Load Engine - PostgreSQL: Enter server address, port, database, username and email.

  94. Load Engine - PostgreSQL: Delta refreshes based on date/time are operational.

  95. Load Engine: Support and adjustments to BigQuery ODBC.

  96. Load Engine: Shows when the load started (metadata date/time).

  97. Command Line: parameter -e <EntityID>. Ex.: -e abccorp

  98. Command Line: parameter -j <JobID>. Ex.: -j 1

  99. Command Line: New command syntax: -e <EntityID> -j <JobID> -ui <Page> <action>.

  100. Command Line: parameter -e <EntityID> -ui load -j <JobID>. Ex.: this runs JobID on a new Load session. This automatically closes once the job completes the refresh.

  101. Command Line: parameter -e <EntityID> -ui log. Ex.: this opens the Log page on a new ETL+ session. This session stays open until the user closes it. Click the Refresh icon to view the latest log rows.

  102. Command Line: parameter -e <EntityID> -ui agent. Ex.: opens the Agent page from an ETL+ session.

  103. Command Line: Engine checks encrypted locally saved credentials when running command lines.

  104. User Interface: Runs a Job on its own window (runs via command line).

  105. User Interface: Opens Agent page on its own window (runs via command line).

  106. Security: New passwords require at least 12 complex characters (up from 8).

  107. Security: New passwords now accept # @ as part of special characters.

  108. Security: When ETL+ can’t connect to its metadata: "Unable to connect to cloud metadata via https and SSL SQL. ETL+ needs to whitelist your public IP, or your firewall or antimalware is preventing ETL+ connection to the cloud. Start ETL+ IP Whitelisting?"

  109. Security: ETL Page - ETL SQL Statement: Clicking Confirm validates zData Warehouse schemas.

  110. Refresh Email Notification: Removed email attachments. No longer necessary with cloud logging.

  111. Log Page: Added Rows Retrieved parameter. Enter a new value and press Refresh icon.

  112. Log Page: (F5) shortcut to refresh Log page.

  113. Log Page: Titles and radio buttons changed to ETL Log and Table Stats.

  114. Log Page: Table Stats layout rearranged and some labels renamed for easier viewing.

  115. Log Page: Default sorting of Log pages is the Index column.

  116. Log Page: Row counting uses SQL metadata (instead of count(*)). Faster performance.

  117. Logging: Checking if Log tables exist only during the opening of an entity (instead of during a load of every table).

  118. Settings: Debug Level dropdown shows a summary of what the log level does.

  119. Settings: Debug Off now removes the log file on the local HD. For saving disk space and avoiding requiring ETL+ to Run as Admin when running from Windows protected folders

  120. Settings: Debug Off no longer counts and records the total number of rows before and after a table load. Performance improvement.

  121. Settings: New Debug Level 0 adds the log file on the local HD plus counts and records the total number of rows before and after a table load.

  122. Settings: Debug Level 1 adds Level 1 log plus Level 0 features.

  123. Settings: Debug Level 2 adds Level 2 log plus Level 0 features.

  124. Restore ETL SQL Statement As Of: New dropdown list on Settings allows users to retrieve prior ETL SQL Server Statements. Useful to recover deleted and changed statements from the past.

  125. Login: Forgot Password? button. It’ll email the password when initiated from whitelisted IPs with a valid username (email address).

  126. Job: New script Download to CSV to run on a schedule. Select a Job+ on the Steps panel -> Download to CSVselect a table -> Save.

  127. Job: Find feature to quickly highlight matches on the Steps panel.

  128. Job: Click the Find icon to expose/collapse the find box.

  129. Job: Standardized user interaction as main ETL page so right-clicking on panel objects pops up the available features. Ex.: right-click a job → Run Job.

  130. Job, left panel: Standardized user interaction as main ETL page so right-clicking on panel objects pops up the available features. Ex.: right-click a job → Run Job.

  131. Job, left panel now has icons on the panel header (instead of inside of the panel).

  132. Job, left panel now has two sets of icons, the left is active when selecting individual jobs, the right is independent of individual jobs

  133. Job, Step panel: now shows the Job <ID> on the header.

  134. Job, Step panel: Added Move to Top icon/feature.

  135. Job, Step panel: Added Move to Bottom icon/feature.

  136. Job, Steps pane shortcut: (Ctrl + F) to go to the Find box.

  137. Job, Steps pane shortcut: select a script → (Ctrl + i) to open its properties.

  138. Job, Steps pane shortcut: select a script → (Ctrl + Del) key to delete.

  139. Job, Steps pane shortcut: select a row → (Ctrl + D) key to pushing it down one row.

  140. Job, Steps pane shortcut: select a row → press and hold the (Ctrl + D) key to push it down.

  141. Job, Steps pane shortcut: select a row → (Ctrl + U) key to pushing it up one row.

  142. Job, Steps pane shortcut: select a row → press and hold the (Ctrl + U) key to push it up.

  143. Job, Steps pane shortcut: (Ctrl + T) to create a new Tableau Extract Refresh script.

  144. ETL+ Plain Deployment: New framework for an on-premises data warehouse that easily loads the zDateUntreated table from a cloud Excel file.

  145. Cloud Scripts: Increased to up to 7 parallel processes.

  146. Metadata: Redesigned metadata for improved security, reporting, and indexing.

  147. Admin user: Remembers the last credentials in DataSelf protected computers.

Fixed Issues

  1. Tables with delta refresh no longer log the misleading message: “Error : Column name '<PK_column1,PK_column2,PK_column3etc>' does not exist in the target table or view.”

  2. Regular users: When login in to ETL+, the list of available entities used to show deleted ones as well.

  3. When manually loading a table, it will retry 3 times in case of failure (instead of 12 times).

  4. Tables with delta refresh no longer run into the error: ‘Invalid column name ‘0_UnionID', but ETL+ still processes the delta refresh correctly.

  5. When super users switched to a new entity within the same ETL+ session could create zEntity and zLog tables in the new entity’s data warehouse with the schema from the prior entity.

  6. When super users switched to a new entity within the same ETL+ session could send refresh emails with the prior entity’s refresh email subject.

  7. Deleting all Jobs no longer requires going to the ETL main page and back.

  8. Deleting an entity and recreating it with the same ID would add a new row to zEntity table.

Known Issues

  1. Clicking the Log icon after certain tasks (such as running a Job) might present an "Unhandled exception" error. Click Quit and re-open. It mostly only happens once.

  2. Regular users: When login in to ETL+, in the first attempt, ETL+ will only open the first entity even when one uses another entity on the dropdown list.

  3. Upon adding a new table from a NetSuite ODBC, the SQL syntax will have an extra ] at the end of the table name. To fix it: remove ] and save.

  4. Many SQL Statements for MongoDB ODBC will only load using SELECT *.

  5. Some Acumatica OData v4 tables might show the error “The contents of table TableName are not available for this user“ and fail to import. This is an Acumatica security issue and we’ve requested how to fix it. While we wait for the Acumatica fix, use OData v3 to import such tables.

  6. Adding tables from Sage Intacct might not work.

  7. Opening an entity from an older metadata version with the new one using a regular user (non Admin) will not update the metadata version in the cloud. Workaround: open it with an Admin user.

  8. Job: If a table fails to refresh, the ETL+ might unexpectedly load several tables multiple times.

  9. Sometimes ETL+ will mistakenly flag that the metadata has been changed and you need to exit and re-enter the entity. Just exit and re-enter.

  10. Changing the data warehouse of an entity won’t show on the bottom left corner until the entity is closed and re-opened.

  11. Regular users: Mousing over Sources doesn’t show the pop up with details.

  12. The icon color and type for the column formats on the center panel aren’t 100% consistent yet.

  13. Opening an entity with tables mapped to the zData Warehouse with an older ETL+ version will push such tables to other source databases on the center panel. DataSelf can fix that manually.

  14. Importing large XML content into varchar(max) might run into error: server stack limit has been reached.

  15. A few installs are hitting the error “There is insufficient system memory in resource pool 'internal' to run this query.” once in a while. It happened to only one table in a job, and a different on another job. Load All. First report started in v2021.09.

  16. Sometimes ETL+ is closing unexpectedly after a data load.

  17. Sometimes ETL+ runs into an “Unhandled exception” error. Close and re-open ETL+.

  18. Locking the ETL+ editing when someone else is editing it doesn’t work in some situations.

  19. ETL+ still tries to send email even when set to Cloud notification, or No Notification.

  20. ETL+ delta extraction from NetSuite ODBC might not work when using dates for filtering.

  21. When opening an entity created in prior ETL+ versions, the data warehouse panel will show the source header blank. To fix this, open the entity in the prior ETL+ version, make any modification and save it. Now open the entity in the latest ETL+ and the source header appears.

...