LDWH 2.0.43 released

The latest DataVirtuality release 2.0.43 brings some minor fixes for the Studio, including bringing back a column to easily identify incremental jobs in the jobs section.

The backend also got a few fixes and improvements, most notably fixing the behavior of the NOW() function inside a block, which now will again return different timestamps if called multiple times inside the block.

Studio

• DVCORE-4825 (Improvement): alphabetically order the list of data sources
• DVCORE-5479: Preferences/SMTP settings cannot be opened
• DVCORE-5473: unable to add Microsoft SQL Server as Analytical Storage
• DVCORE-5471: edit of AdWords datasource sets UserAgent as translator property
• DVCORE-5461: increase default memory settings
• DVCORE-5460: chainString is incorrectly displayed and exported and causes errors on opening Jobs tab
• DVCORE-5469: bring back incremental column in Jobs window

Connectors

• DVCORE-5470: FTP connector: "listFiles" procedure returns nothing in some cases
• DVCORE-5459: Netezza: non-Latin symbols are returned as question marks if data source added with ODBC connection

Backend

• DVCORE-3763 (Improvement): Introduce a more compact syntax for calling stored procedures without using EXEC or CALL
• DVCORE-5464: NOW() function returns the same value for each call in BEGIN...END block
• DVCORE-5457: DataVirtuality Exporter: CLI tool bundled with DataVirtuality Server is not compatible with embedded JDK
• DVCORE-5453: DataVirtuality Exporter: SMTP settings are not correctly exported for releases prior to 2.0.41
• DVCORE-5472: DataVirtuality Exporter: MAX_DECODER_OBJECT_SIZE value for huge import block is set inside it
• DVCORE-5425: Import of views and procedures depending on multiple objects is extremely slow in case of long chain of dependencies
• DVCORE-5391: DataVirtuality Server allows creation of a second schedule for cleanup jobs
• DVCORE-5311: Deleting from temp tables based on id from a physical table throws an exception
• DVCORE-5164: Implement handling of NUMERIC precision limit of 38 for Microsoft SQL Server and Redshift
• DVCORE-5091: Buffer defrag is not working correctly
• DVCORE-4348: System queries containing UNION ALL are visible in query monitor
• DVCORE-4183: MULTIPLE indexes are attached to the wrong recommended optimizations for JOIN queries
• DVCORE-3641: Joining results of table functions one of which uses results of another one causes error
• DVCORE-3639: Joining more than one table/view to results of table function causes error