February 11, 2016 Leave a comment
This is a major new version of BISM Normalizer. It can be downloaded from a different Visual Studio Gallery page. The current version will run for free till June 30th 2016.
Visual Studio 2010/2012/2013 (SQL Server 2012/2014) are not supported by BISM Normalizer 3. For these, you can still use BISM Normalizer 2. See the Purchase page for more info on version compatibility.
Enhancements in Version 18.104.22.168
Support for SQL Server Analysis Services 2016 CTP3.3 and Visual Studio 2015
SSAS compatibility levels 1200, 1100 and 1103 are all supported.
JSON definitions with improved difference highlighting
Support for DirectQuery models with compatibility level 1200
Both source and target models must have the DirectQuery Mode property set to On for successful comparison.
Processing on database deployment
When deploying to a database (not project), BISM Normalizer will check connections set up for impersonation, and prompt for username and password (like deployment from SSDT).
Like SSDT, processing options include “Default”, “Do Not Process” and “Full”. There is an option to process only the tables affected by the comparison (Create and Update), to avoid unnecessary processing.
Switch source and target in Connections dialog
Improved scripting for JSON and XMLA
BISM Normalizer will use the appropriate editor if available. If not, can save to a file instead. Note: the JSON editor is not installed as part of a SSDT only installation with the Visual Studio Integrated Shell.
View code behind BSMN file
Allows viewing and manual setting of values in BSMN files.
Associate BSMN file types with Visual Studio
Open BSMN files direct from Windows Explorer with Visual Studio as the default application. Also set up BISM Normalizer icon for Solution Explorer. To enable this, right click a BSMN file in Solution Explorer and select the Install Solution Explorer Icon context menu. Note: administrator permissions are required to even see the menu option. This can’t be set up automatically with standard VSIX deployment from the Visual Studio Gallery because of the admin requirement.
Upcoming features for next release
Targeted for Release 3.1: command-line execution passing BSMN file as a parameter. This will allow integration with automated builds/deployments.
Translations are currently not supported by BISM Normalizer 3. Until this Connect bug is fixed, the target model will not contain translations, even if they were present before the comparison. The current version strips out translations when doing an update.