Virtual Data Warehouse v1.7.0

New features

• Added a feature to separate mapping lists into separate files (template grid)
• Additional work on high DPI / scaling (this is also the reason the filter and generate to move up)

Breaking changes

N/A

Bug fixes

• Special characters in metadata (JSON) such as <>=" are now possible to be used in templates.

Virtual Data Warehouse v.1.6.14

New features

• Adding multi-session support for Snowflake, so that multiple queries can be executed in a single call (database setting permitted)
• Adding filter that shows enabled mappings in the list of objects. Unless explicitly disabled using the Hide Disabled Mapping checkbox, Data Object Mappings that are disabled (enabled = false) are not taken into account

Breaking changes

N/A

Bug fixes

• Update of dependencies / references to the respective latest versions
• Update of Snowflake libraries

Virtual Data Warehouse v.1.6.13

New features

• Snowflake connection feature, VDW code now connects and runs code against a Snowflake-configured connection.
• Additional improvements on high-DPI support, this should address various issues around overlapping controls on monitors with 125% or 150% scaling.

Breaking changes

N/A

Bug fixes

N/A

Virtual Data Warehouse v.1.6.12

New features

• Additional templates, including for data object creation
• Uses the latest DataWarehouseAutomation NuGet package / class library which has various additional functions to use in the templating engine.
• Sample updates for consistency and adding various use cases, for example more complex transformations.

Breaking changes

• Removed the backup feature when saving templates. All projects are using Git, so having a redundant backup on each save became really annoying.
• Removed syntax highlighting on SQL output. Most projects directly access the output in SQL clients, and the highlighting really slows down the processing. It could be created on a separate thread but since it's rarely used it's quicker and easier to just disable for now.

Bug fixes

• Fixed bug that saved output to disk even when the 'save output' checkbox was not checked.
• Fixed a bug that prevent output to directly be generated against a SQL Server family database.

Virtual Data Warehouse v.1.6.11

New features

• Ability to switch between environments without having to restart VDW. Changing environments will now correctly update all paths and refresh the template collection and available metadata. Also, updating the location of the template collection (for the template grid) will directly refresh the available templates
• Major update of all templates to align to the latest standards and understanding (especially for Data Vault). There are no functional changes, but the templates have been improved to cater for additional edge cases or different approaches as captured in the updated samples. For example, issues were found mapping a single data item to multiple target data items. In many cases the handling of trailing commas is also improved
• Upgraded all references, including latest DataWarehouseAutomation library
• Upgraded solution to .Net 7 (to Core from Framework 4.8)
• Moved all paths to the (Team) environment file, so everything that is required is available in a central shared location. Removed connections path as a result from the settings tab

Breaking changes

• No breaking changes

Bug fixes

• Fixed unhandled exception when an incorrectly formatted template collection file was attempted to be loaded

Virtual Data Warehouse v.1.6.10

New features

• A significant number of load patterns / templates has been added to the collection of available templates
• Better resizing of the template collection grid

Breaking changes

The term 'Load Pattern' has been replaced with 'Template' everywhere. This is not noticeable in most cases except for some labels, except for the following two scenarios:

• In the VDW_Configuration.txt file (Core directory), the entry 'LoadPatternPath' has been replaced with 'TemplatePath'. You can update this manually or re-set the path in the application, in which case this entry will be added.
• The JSON file that contains the list of load patterns/templates has been renamed from loadPatternCollection.json to templateCollection.json. In addition, the segments have been renamed, for example:

  {
    "templateName": "Data Vault Hub 001 View Template",
    "templateType": "CoreBusinessConcept",
    "templateConnectionKey": "PsaConnectionInternalId",
    "TemplateOutputFileConvention": "{targetDataObject.name}.sql",
    "templateFilePath": "templateHubView.handlebars",
    "templateNotes": "Standard Hub template - display the distinct list of Business Keys for a Core Business Concept."
  }

The reasoning behind this is to standardise the naming to how they are used in the various related initiatives. The term 'pattern' is reserved for more conceptual explanation of certain concepts and approaches. The term 'template' is used to identify a technology-specific code (generation) version of this.

Bug fixes

• More detail on SQL error messages, in case there is an issue generating SQL directly against the database

Virtual Data Warehouse v.1.6.9

New features

• Better form resizing and overall performance
• Exception handling on tab pages
• Moved more syntax highlighting to separate thread

Bug fixes

• Fixed issues related to correctly establishing database connection
• Fixed issue related to configuration paths now showing correctly. They were working fine, but showing the wrong path in some scenarios

Other

• Update of all references

Virtual Data Warehouse v.1.6.8

The Virtual Data Warehouse (VDW) v1.6.8 version contains various smaller changes to keep in sync with TEAM. This version works best with v1.6.6. although earlier versions still work.

The main improvements are:

• Grid performance improvements
• Better switching between environments, this now inherits the configuration and metadata paths
• Added a feature to specify an output file format for each template (in the load pattern grid)
• Better syntax highlighting performance
• Better use of screen real-estate
• Added single / embedded executable to avoid MSI installation restrictions, if applicable

What's Changed

• V168 by @RoelantVos in #17
  Full Changelog: v1.6.7...v1.6.8

Virtual Data Warehouse v.1.6.7

VDW 1.6.7 is a minor revision that has been created to support TEAM 1.6.5, since this release introduced a breaking change to the patterns – namely the Dimension pattern.

The main difference is that in previous TEAM versions, the generated Dimension JSON file combined the various sources from all data object mappings into a single data object mapping (with multiple source data objects mapping to a single target data object).

In TEAM 1.6.5, each data object mapping is generated as a single dataObjectMapping segment in the target Dimension JSON. This means that the Dimension JSON file contains three segments in the provided example data.

In the pattern, this has been addressed by wrapping a {{#each dataObjectMapping}} everywhere where the {{sourceDataObjects}} are used.

Virtual Data Warehouse v.1.6.6

Minor template fixes due to upgrades / changes in the templating engine.