Attention

This document is no longer being updated. For the most recent documentation, including the latest release notes for version 6, please refer to Documentation Version 7

Release Notes - Version 5

5.5.4.2

(29.07.2022)

Security Release updating docker images. Final release for version 5!

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.5.4.1

(27.05.2022)

Security Release updating docker images.

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.5.4.0

(08.04.2022)

Security Release updating docker images.

Other changes:

  • Neo4j: Removed driver from DVB due to log4j vulnerability. Please check the documentation section “Staging” for manually including the driver if needed.

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.5.3.2

(04.03.2022)

Security Release updating docker images.

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.5.3.1

(26.01.2022)

Security Release updating docker images.

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.5.3.0

(20.12.2021)

Security Release

Other changes:

  • Log4j: Updated to 2.17.0 to fix CVE-2021-45105 and CVE-2021-45046.

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.5.2.0

(13.12.2021)

Security Release to fix CVE-2021-44228. The update is recommended for all clients to prevent such attacks on the system.

Datavault Builder is affected by CVE-2021-44228 to a limited extent:

  • As long as the user is not authenticated, no such attacks are possible.

  • However, as soon as a user is logged in, the vulnerability can be exploited by that user.

This update increases the used version for log4j to 2.15.0 to resolve the CVE.

Workaround

If you can not update to this version immediately, you can apply changes in your docker-compose.yml to prevent the CVE, too, by setting log4j option formatMsgNoLookups.

Please have a look at the corresponding knowledge base article here: https://kb.datavault-builder.com/display/DBKB/Installation

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.5.1.0

(20.08.2021)

Improvements:

  • Oracle: Handle mat view refresh to also support broken mat views without comment.

  • Exasol: Support for Exasol version 7.1.0 .

  • MS SQL: Faster link data deletion.

  • Staging: New Source Type available: Added Amazon Redshift.

Behavioral Changes:

  • General: Introduced automated cache maintenance.

Other Changes:

  • Exasol: Updated clientdb image to use Exasol 7.1.0

  • Exasol: Updated JDBC driver (7.1.0).

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: Yes / No - Exasol 7.1 has introduced TLS for all connections. As a part of the TLS handshake, the drivers require SSL/TLS certificate used by Exasol to be verified. This might needs configuration adjustments for the connection string used to connect to the database or the database itself. Please check https://www.exasol.com/support/browse/EXASOL-2936 for details.

  • Snowflake: No / No

5.5.0.0

(30.07.2021)

Improvements:

  • General: Changed logging behavior: Logs are written batchwise instead to improve performance and stability, especially when executing large job loads.

  • Snowflake: Changed persisting view relations onto database: View relations changes are written batchwise to improve performance and stability.

  • Snowflake: Improved putting columnar metadata to speed up object creation and modification.

Bugfix:

  • General: Fixed authentication against database.

  • General: Fixed dialogues gradually hiding scroll.

  • Business Rules: Fixed issue with updating view dependencies after saving.

  • Data Lineage: Fixed circular dependencies switch (hint: will still only take affect once at least one filter is defined).

  • Snowflake: Fixed when using columns of data type float as part of business key.

  • Exasol: Fixed issue with update process potentially trying to re-execute hashtype update.

Behavioral Changes:

  • Staging: If a general subset and a delta load subset condition is defined, they will be now explicitely grouped as “(general filter) AND (delta filter)”.

Other Changes:

  • Snowflake: Updated Snowflake Driver (3.13.5).

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.4.8.0

(30.06.2021)

Improvements:

  • General: Reduced memory usage of datavault builder core engine.

  • Staging: New Source Type available: Added Databricks.

Bugfix:

  • Staging: Set interbase source connector by default to sqlDialect=3 to handle quotes properly.

  • Datavault - MSSQL: Fixed an issue preventing binary data type to be loaded as part of a business key.

  • Operations: Prevent a job from executing its post job query multiple times.

  • General: Fixed an issue causing a failed authentication to lead to multiple failed login attempts.

  • MS SQL / Azure SQL: Fixed install script for Azure SQL database.

  • Datavault: Fixed potential issue “cannot read css of null”.

Other Changes:

  • Staging: Updated Datavirtuality Driver (2.4.7).

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.4.7.0

(09.06.2021)

Improvements:

  • Operations: Jobs without loads are finished faster.

  • Security: Allow usage of custom impersonation command. With this, its for instance possible to have user roles prefixed.

Bugfix:

  • Staging - Snowflake: Fixed issue with storing systems containing backslashs in its parameters.

  • Staging: Fixed issue with denormalize parameter not working for xml/json source.

  • Staging: Fixed broken data preview for source tables.

Other Changes:

  • Staging: Updated gRPC-Connector.

  • Staging: Updated DB2 AS400 driver (10.6).

  • MS SQL: Updated JDBC driver (9.2.1).

  • Exasol: Updated JDBC driver (7.0.7).

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.4.6.0

(27.05.2021)

Improvements:

  • Staging: New Source Type available: Added DB2 for LUW.

  • Staging: New Source Type available: Added DB2 for IBM i.

Bugfix:

  • Datavault - Snowflake: Explicitly lock hub on load to prevent parallel load potentially leading to duplicated business keys.

  • Staging - MS SQL: Fixed issue potentially preventing edit of staging tables with defined loads.

Other Changes:

  • Staging: Updated gRPC-Connector.

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.4.5.0

(14.05.2021)

Bugfix:

  • Datavault: Fixed issue trying to load satellites without staging table in jobs.

  • Business Rules: Fixed issue removing block comments from views.

  • MS SQL - Accesslayer: Fixed an issue preventing the accesslayer to be automatically updated when editing a business ruleset.

  • Staging: Fixed an issue with float data type conversion for Excel and SQLite sources.

  • Staging: Fixed an issue preventing the actual error to be logged in some cases.

Other Changes:

  • Staging - SQLite: Updated JDBC driver (3.34.0)

  • Staging - Data Virtuality: Updated JDBC driver (2.4.4)

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: Yes / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.4.4.0

(23.04.2021) In this release we have added new sources. For some of them, due to (license) restrictions, we can not distribute the driver with Datavault Builder directly. Please have a look at the documentation (Main Manual > Modules > Staging) for details on how to enable those source types.

Improvements:

  • Staging: New Source Type available: Added SAP HANA (Driver is not distributed).

  • Staging: New Source Type available: Added InterBase (Driver is not distributed).

  • Staging: New Source Type available: Added ElasticSeqarch.

  • Business Rules: Improved edit performance.

Bugfix:

  • Dimensional Model - Exasol: Fixed an issue removing the businessobject structure when editing a business object.

  • Deployment: Fixed an issue causing satellite deployments to fail in case certain columns are not used for load anymore.

  • Postgres: Fixed postgres install scripts.

  • MS SQL: Corrected user grants for new installs.

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.4.3.1

(24.03.2021)

Bugfix:

  • Snowflake: Fixed loads to throw error again if a duplicate is detected within a load.

  • Cache Maintenance: Fixed an issue preventing maintenance tasks from automatically refreshing caches.

  • Dimensional Model: Fixed permission for dvb_user_readonly to be able to see dimensional objects.

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.4.3.0

(15.03.2021)

Improvements:

  • Postgres: Added support to load postgis datatype “geometry”.

  • Staging: Improved error-handling for intra-/cross-database loader.

Bugfix:

  • Dimensional Model: Fixed an issue not allowing to create new business object with pending suffix_id validation.

  • Business Rules - Exasol: Fixed an issue causing renaming of business ruleset to fail or make business rule uneditable.

  • Deployment: Fixed issue showing “” instead of null (e.g. for staging table properties comment or where clause and business ruleset comment)

  • Data Lineage: Fixed handling of multiple search terms.

Behavioural Changes:

  • Business Rules: Except for postgres, custom view dependencies on top of business rules and accesslayer are not checked / recreated anymore but remain as they are.

Other Changes:

  • Exasol: Updated clientdb image to use Exasol 7.0.7

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: Yes / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: Yes / No

  • Snowflake: Yes / No

5.4.2.0

(26.02.2021)

Improvements:

  • Configuration: Introducing parameter “index_storage” (in table dvb_config.config): If specified and depending on database type, will create future indices (also for primary keys) on this tablespace (e.g. Oracle/Postgres) or filegroup (MSSQL).

  • Business Rules: Improved search speed.

Bugfix:

  • Documentation: Fixed broken pdf export of documentation.

  • Deployment: Fixed broken filtering for domain and object type.

  • Staging: Fixed initiating source system to also trigger previously failed staging loads again.

  • Exasol: Fixed issue causing error updating metadata of objects (e.g. updating subject area, column comment, ..).

Behavioural Changes:

  • MS SQL: New install of clientdb will automatically set database recovery model to simple.

Other Changes:

  • User Role - dvb_operations: Extended dvb_operations API privileges for getSourceSystem.

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: Yes / No

  • Snowflake: No / No

5.4.1.0

(08.02.2021)

Bugfix:

  • Data Viewer: Fixed potentially missing staging tables for certain systems.

  • MS SQL: Fixed issue failing the initial install on databases with custom name (other than datavaultbuilder).

  • Oracle: Fixed broken oci connector.

  • Snowflake: Fixed potentially failing staging load by catching missing “_DVB_ROW_ID” in staging table during load.

Behavioural Changes:

  • MS SQL: In business vault loads, column datatypes (e.g. varchar, varbinary) are not automatically extended to max anymore. Instead, they keep the precision as specified in the business ruleset column.

Other Changes:

  • Staging - MS Access: Updated JDBC driver (5.0.1)

  • Oracle: Updated JDBC driver (21.0.0.0.0)

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.4.0.0

(19.01.2021)

Improvements:

  • Webgui: Added docker parameters to influence NGINX timeouts via docker-compose.yml (PROXY_CONNECT_TIMEOUT, SEND_TIMEOUT, PROXY_READ_TIMEOUT, PROXY_SEND_TIMEOUT)

  • Staging - Files: Assigned a fixed user with UID/GID 2150 for data uploads. If you are unable to read or edit existing files already present in “/files”, then execute the following to update the files permissions: docker-compose exec -u0 connection_pool chown -R 2150:2150 /files

  • Staging - CSV: Directly allow usage of escaped string parameters, so values do not have to be overwritten in connection string manually (e.g. for TAB use t)

Bugfix:

  • Operations: Fixed converting job type (auto to manual) while conserving selected loads.

  • Operations: Fixed issue to prevent orphaned job load entries (e.g. deleted hub load) leading to failed job loads.

  • Operations: Fixed status message overflow.

  • Data Preview: Fixed null returned for all consecutive values if a hashtype field was null.

  • Data Viewer: Fixed error can not get array length of null.

  • Data Viewer: Fixed error when previewing hash fields.

  • Deployment: Fixed missing hub/link dependency detection in deletion.

  • Business Rules: Fixed potentially added linebreaks in business rules leading to difference in deployment.

  • Datavault: Fixed an issue which could reset the link suffix id during link creation.

  • Staging: Fixed an issue when changing source type of an existing source having to “revert” connection string after every letter.

  • MS SQL: Fixed rehashing update process for links.

  • MS SQL - Staging: Fixed type mapping for float datatype.

  • MS SQL: Fixed potentially undetected errors in ddls and thereby related cache going out of sync.

Other Changes:

  • User Role - dvb_operations: Extended dvb_operations API privileges to additional load related APIs as well as APIs necessary to view load or job states in the GUI.

  • Exasol: Updated clientdb image to use Exasol 7.0.5

  • Exasol: Updated JDBC driver (7.0.4)

  • Postgres: Updated clientdb image to use Postgres 13.1 & Postgis to 3.0.3

  • General: Added docker parameter to set log level for core and connection_pool (LOG_LEVEL)

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.3.3.1

(04.12.2020)

Improvements:

  • Snowflake / Exasol - Datavault: Adjusted load patterns for satellites and transaction links, removing unneeded join condition which could slow down loads.

Bugfix:

  • MSSQL - Staging: Fixed an issue potentially failing the edit of staging tables with defined hub loads on MS SQL.

  • Snowflake: Fixed an issue, which could report duplicates in load for empty staging tables while loading.

  • Staging: Fixed an issue returning an error for missing columns containing ‘.’ when editing a staging table.

Other Changes:

  • Staging: Updated CSV Driver to 1.0.36, resolving issue with indexedFiles and fileTailPrepend when having missing line breaks in files.

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.3.3.0

(20.11.2020)

Improvements:

  • General: Better performance due to improved logging.

  • Staging: Better error handling when trying to create staging tables with columns containing “.”.

  • Staging: Better error handling when data preview for the source type is not supported.

  • Datavault: Business Key Duplicate Checker warns if the checked staging table is empty.

  • Datavault: Business Key Check is by default in unchecked status.

Bugfix:

  • Exasol - Datavault: Fixed an issue, where the edit of a satellites metadata could corrupt the SCD2 Type View Output, which could also prevent the overall startup.

  • Datavault: Fixed an issue potentially showing wrong data types in satellites / transaction link metadata.

  • Staging: Fixed an issue, which could fail staging loads with “unkown type” error.

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / Yes

  • Snowflake: No / No

5.3.2.3

(17.11.2020) Internal Release

5.3.2.2

(16.11.2020)

Improvements:

  • Datavault: Aligned and improved error messages for deletion.

Bugfix:

  • Staging: Handle diverging metadata of source driver for MS SQL Bulk Loader (e.g. CSV Driver returns “ss” instead of “ẞ” as column name for the resultSet).

  • Staging: Fixed Data Preview of staging table / source table for supported source types.

  • Staging: Fixed occasionally disappearing lines in staging module.

  • Dimensional Model: Fixed using space in column names.

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.3.2.1

(04.11.2020) Internal Release

5.3.2.0

(27.10.2020)

This update includes a major model upgrade. Make sure to follow the update instructions and do perform the update on a backed up environment first! Depending on the size of your model and data volume, this update will take several hours to complete. After following the update steps and starting up the environment again, do check the core logs “docker-compose logs -f core” for any error message thrown during the upgrade steps.

Besides numerous performance improvments in the UI, we are introducing a further optimized technical implementation for all supported target databases, based on a SCD Type 4 approach.

Up to date, the implementation of object historization was done with a SCD Type 2 (ending to _H) and a SCD Type 1 (_C) object, whereof the content contained within the SCD1 version was also part of the SCD2 object. This meant, that the latest version of the data was basically stored twice.

With our newly released SCD4 approach, this pattern will be discontinued. Instead, an additional object (SCD4) is introduced:

  • The SCD4 Object (_A) will only hold the history, not the current information.

  • The SCD1 Object (_C) will only hold the latest state, no historical information. (It provides the same data as before)

  • The SCD2 Object (_H) will combine both parts to provide the whole history including the latest state. (It provides the same data as before)

The advantage of this is: Faster loading performance (less I/O), less disk space used and simplified management of historical data.

Please check the list below for further improvements and also have a look at our training video section: We added more videos, e.g. about the deployment and code versioning process.

Improvements:

  • General: Better responsiveness and performance

  • General: Better loading performance and storage need due to SCD4 approach

  • Datavault: Display conversion type settings and complete data type in Satellite / Transaction Link Metadata Slider.

  • Snowflake: Updated JDBC Driver (3.12.13), drastically increasing staging speed for time

  • Snowflake: Improved metadata getters to allow the Snowflake optimizer to return metadata quicker.

  • Postgres/MS SQL/Exasol/Snowflake: Increased data type size of row_id to handle larger batches.

  • Deployment: Switch deployment direction does not reload models anymore to allow faster comparison.

  • Staging: Allow cancel test source connection on first try.

  • Staging: Replaced complete staging module in the UI with faster engine.

  • MS SQL: Replaced computed columns with “Instead of” triggers for hash key computation, avoiding schema locks during modelling.

  • MS SQL: The amount of loaded data in the staging tables will no longer slow down the modelling performance when adding new loads.

  • Staging: General introducation of an “Intra / Cross Database Loader”. This allows direct loads within the target instance, which is much faster than using regular source connectors when performing loads within the same target environment. (Cross DB loading is only supported on Snowflake and MS SQL for technical reasons e.g. loading from one MS SQL Database into the Datavault Builder MS SQL Database - Intra DB loading from inside the Datavault Builder Database is possible on all Databases)

  • Exasol: Make use of built-in JSON Functions. This increases the required minimum version for DVB to Exasol 6.2.7

  • MS SQL: Updated JDBC Driver to 8.4.1.

  • MS SQL: Enabled the bulk copy feature again for better staging performance

Bugfix:

  • MSSQL: Rehashing the hub and links hashs, preventing a potential issue with spaces, varchar/nvarchar bks and link hash composition. As the comparison between staged an already loaded business keys is now executed on a binary level even differences that MSSQL treats incorrectly the same are now recognized correctly as different. Example “123” and “123 “ were treated as the same value in the past but will now both be loaded separately. This can lead to new rows being added into your vault.

  • Deployment: Unaltered Default BRs could show difference. Switched the export format to include a column list instead of the code to make the compare stable.

  • Deployment: Job load deletions are now correctly rolled out.

  • Business Objects: Related BO now shows the correct information.

  • Business Objects: Fields of objects were sometimes not available anymore when they were already used in a related BO.

  • SQL Editor: Enabled “Home” & “End”

  • MS SQL: Cleanup of potentially duplicated values in Link History (only affects installs coming from Version 4.0.5.0)

  • Staging: Manually altered connection string was stored, but on edit not retrieved/displayed correctly.

  • SQL Editor: Fixed issue where sometimes only 2 or 3 lines were visible.

  • Business Objects: Fixed an issue where not all fields could be refactored in the GUI.

  • Satellites/Transaction Links: Fixed an issue where the cache and the actual metadata of the objects could get out of sync.

  • Staging: Fixed an issue, where the source system creation could fail due to missing colors in the system colors pool.

  • Snowflake: Fixed reading column conversion from Database

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: Yes / Yes - 1. To properly enable the “Intra / Cross Database Loader”, the database users will now be assigned to a (disabled!) login on master database level. This is part of the update scripts. One of the update Scripts (mssql_update_masterdb) will create the logins on the master db level. This script has to be executed first. Then, the second script (mssql_update_clientdb) will drop the existing users and recreate them assigned to the login just created. HINT: In case you are using a custom user instead of the authenticator, make sure to replace “authenticator” in the scripts with “authenticator, YOURUSERNAME”.

  • Oracle: Yes / Yes

  • Postgres: Yes / Yes

  • Exasol: Yes / Yes 1. New mininum Exasol Verion is 6.2.7 - 2. In case you are upgrading DVB and also going to Exasol 7, make sure to include EXASOL_USE_CHAR_FOR_HASH=true as environment variable for the core service in case you would like to continue using CHAR instead of HASHTYPE for the hash fields. Otherwise, the update will automatically alter the field type. 3. The default port within the exasol docker container has changed to 8563. If you are upgrading an existing environment with exasol running within a docker container, you will need to add ENVIRONMENT_DATABASE_DB_PORT=8888 to the service environment variables to overwrite the used port.

  • Snowflake: Yes / Yes 1. To properly enable the “Intra / Cross Database Loader”, replace in the CLIENT_DB_CONNECTIONSTRING variable of the core service in your docker-compose.yml the part CLIENT_METADATA_REQUEST_USE_CONNECTION_CTX=true with CLIENT_METADATA_REQUEST_USE_CONNECTION_CTX=false&CLIENT_METADATA_USE_SESSION_DATABASE=true

5.0.0.0_b2.8

(28.08.2020)

Snowflake: Handle changed behavior of RIGHT Function

Improvements:

  • Staging: Added MariaDB as a source type.

  • Staging: Added SQLite as a source type.

  • General: Updated Snowflake JDBC Driver to 3.12.11

  • MS SQL: Performance improvement as the database is not called anymore for quotename

Bugfix:

  • Staging: Fixed potential escaping problem of staging table columns during staging load

  • Snowflake: Handle changed behavior of RIGHT Function

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: Yes / No

5.0.0.0_b2.7

(06.08.2020)

Improvements:

  • Staging: New Source Type available: Added Amazon Athena.

  • General: Handle display zoom if custom scaling is defined.

  • Deployment: Handle broken dependencies by notifying user, e.g. if a business rule references a non existing business object.

Bugfix:

  • Data Vault: Fixed delete satellite dependency check to be less sensitive.

  • Staging: Initiating a system load while a staging load was running caused “invalid input syntax” error

  • Data Lineage: Fixed clause leading to lineage being stuck in “not up to date” unless manually refreshed

  • Dimensional Model: Do not reset manual ordering of Businessobject when using “double-click” or “+”

  • Documentation: Store initiating username instead of servername.

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.0.0.0_b2.6

(16.07.2020)

Improvements:

  • Snowflake: Updated JDBC Driver, drastically increasing staging speed (known limitation: based on our tests, the driver does not yet allow this for all data types , e.g. time)

  • Oracle: Extended data type for BK column in hash to NVARCHAR(2000)

Bugfix:

  • Deplyoment: Fix export of columns with pattern “_dvb_”

  • Dimensional Model: Fix renaming and commenting

  • Exasol: Fixed deleting Businessobject with dependent unaltered business rule

  • Data Lineage: Fixed missing Business Vault Systems in Job Lineage

  • Dimensional Model: Fixed replacing of columns

  • Deployment: Fixed hub load dependencies selection

  • Deployment: Do not call deleteHubData for alias hubs

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: Yes / No

5.0.0.0_b2.5

(02.07.2020)

Improvements:

  • Oracle: Performance of base views

  • Connection Pool: Stability improvements (impacting also loading stability)

  • Documentation: Moved documentation storage into core for compatibility. This means, the documentation has to be regenerated after removing the core container.

  • Business Rules: Open underlying Business object directly from the business rulesets list

  • Deployment: If retry of a failed deployment is successful, overwrite failed state

Bugfix:

  • Operations: Fixed editing jobs, so it directly updates the information without a need for a cache refresh

  • Operations: Fixed command line content to not be overwritten / reset when switching from module

  • General: Re-Enabled edge-chromium support

  • Documentation: Fix “Cannot read property ‘regenerate’ of undefined

  • Oracle: Filter recycle bin objects so that startup/caching is not affected

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: Yes / No

  • Oracle: Yes / No

  • Postgres: Yes / No

  • Exasol: Yes / No

  • Snowflake: Yes / No

5.0.0.0_b2.4

(26.06.2020)

Improvements:

  • General: Allow copying of result/error messages. Prevent Overflow of messages.

Bugfix:

  • Connection Pool: Prevent insufficient privileges error

  • Datavault: Return error if updating metadta fails

  • Operations: Fixed escaping of single quote ‘ in job schedule parameters

  • Business Rulesets: Fix access errormart related problems, potentially not allowing to edit a view and having outdated access errormarts

  • Datavault: Fix bookmark restoring

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.0.0.0_b2.3

(22.06.2020) Internal Release

5.0.0.0_b2.2

(28.05.2020)

Improvements:

  • Business Rules: Handle business rules missing include_in_accesslayer in metadata

Bugfix:

  • Staging: Fix loading time type. Hint: On exasol milliseconds are not yet loaded

  • Datavault: Fixed escaping of mssql satellite and transaction link creation (datavault staging view)

  • General: Fixed potential race condition issue in connection pool

  • Exasol/Snowflake: Fixed caching issue in hub and link load deletion, causing other loads from the same staging table to fail

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.0.0.0_b2.1

(20.05.2020)

Bugfix:

  • Exasol: Corrected type mapping for integer values in staging

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.0.0.0_b2.0

(15.05.2020)

Improvements:

  • Deployment: Compare Environment Configurations to show if the environments behave differently

  • Jobs: Extend sql post job queries length on oracle, exasol and snowflake, also extend error messages in log tables

  • Datavault: fix Do not open search bar if object present

  • Command Line: Command line CTRL + ENTER to do the same as CTRL + S

  • Deployment: Allow direction changes before connecting

  • Command Line: Handle long error messages and let user copy it

Bugfix:

  • Staging: Handle Citext Type on postgres and default to string otherwise

  • Deployment: Handle dependencies when selecting top categories (Data Vault, Staging, …)

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: Yes / No

  • Postgres: No / No

  • Exasol: Yes / No

  • Snowflake: Yes / No

5.0.0.0_b1.27

(08.05.2020)

Improvements:

Bugfix:

  • General: Escape JSON Strings in comments

  • General: Row counts in same transaction as the load, otherwise the count may be wrong in the log

  • General: Ensure transaction are commited or rollbacked before triggering dependent loads

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.0.0.0_b1.26

(30.04.2020)

Improvements:

Bugfix:

  • Exasol: Fixed exasol bug for special characters in comments (or other metadata)

  • Staging: Fixed issue when äöü (or any other unicode escape sequences) occurs in source filename or sheet name (e.g. excel)

  • Businessobjects: Handle different names for related Businessobjects

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.0.0.0_b1.25

(23.04.2020)

Improvements:

Bugfix:

  • Staging: Compatability Fix for JDBC Drivers wrongly using column names instead of column labels

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.0.0.0_b1.24

(20.04.2020)

Improvements:

Bugfix:

  • Staging: Let ‘-’ sign be a valid character in source_staging_table_id (coming from the source)

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.0.0.0_b1.23

(16.04.2020)

Improvements:

Bugfix:

  • Staging: Fixed issue when opening staging table properties after loading a staging table was not possible

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.0.0.0_b1.22

(09.04.2020)

Improvements:

Bugfix:

  • Snowflake: Changed business key generation by adding coalesce

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: No / No

  • Postgres: No / No

  • Exasol: No / No

  • Snowflake: No / No

5.0.0.0_b1.21

(08.04.2020)

Improvements:

  • Staging: Fixed Excel Connect

  • Businessrules: Remove not existent objects from quick inserts

Bugfix:

  • Oracle/Snowflake: Deploy Columns with conversions

  • Exasol: Cached Metadata of columns (conversion, name, comment)

  • General: Prevent “no valid connection available” error during loads

  • Snowflake: Allow load of sat > 2 Billion records (variable overflow)

  • General: On startup log in core log if a failure happens (refresh config)

Hints for the Installation: Manual Update Scripts / Automatic Model Update

  • MS SQL: No / No

  • Oracle: Yes / No

  • Postgres: No / No

  • Exasol: Yes / No

  • Snowflake: Yes / No

5.0.0.0_b1.2 - 5.0.0.0_b1.20

Internal test releases

5.0.0.0_b1.1

(04.11.2019)

First Beta Release with Connection Pool and Cache.