BISM Normalizer: Version 3.4 Released!

Download it from the Visual Studio Marketplace.

Enhancements in Version 3.4

Support for Visual Studio 2017

Like the SSDT for AS extension, BISM Normalizer 3 now works with Visual Studio 2017.

BISM VS 2017

BISM Normalizer 3 continues to work with Visual Studio 2015.


Version bumped TOM references to version 14

This removes the pre-requisite from version 3.3 to install the latest client libraries for Azure AS, which caused compatibility issues for some users.


1400 models not yet supported

1400 models are not supported by this version. If you want BISM Normalizer to work with 1400 models, please vote up this item!

BISM Normalizer: Version 3.3 Released!

Download it from the Visual Studio Gallery.

Enhancements in Version 3.3

Support for Azure Analysis Services!

Azure AD role members work.

aad-members


BISM Normalizer is free and open source!

Removed obfuscation and expiration date. Here is the GitHub page.


Better compatibility with integrated workspace server

In the previous version, if attempt comparison where source/target is a project hosted in integrated workspace mode, and SSDT has just been opened, and the .bim file was not previously left open (so has not been opened yet in the new SSDT session), would fail to connect to workspace server (was necessary to open .bim file and try again). This is now working off the bat; will connect to the integrated workspace server without having to open the .bim file first.

 

BISM Normalizer 3 Use Cases

BNormLogo3_blog

SSAS Compatibility Level 1200

  • Consider BISM Normalizer 3 to deploy tabular models with the awesome new SSAS features
Check

Command-Line Execution

Check

Script Generation

Check

Processing on Deployment (UI Mode)

Check

Retain Partitions & Role Members

  • Retain partitions set up by ETL processes
Check

Visual Studio Integration

Check

Allow Multiple Deployment Strategies

Partial deployment

  • Deploy bug fixes without unfinished features in development
  • Incrementally deploy SSAS objects in isolation, providing flexibility for changing requirements

Traditional all-or-nothing deployment

  • Requires a Production code branch for bug fixes. Use BISM Normalizer to merge bug fixes to the main branch, avoiding manual fix in two different places.
Check

Merging of Tabular Models

  • Pick and choose objects to reuse in other models
  • Merge Power Pivot migrated models into existing corporate models
  • Standardize SSAS objects used by different groups/developers in an enterprise organization
Check

BISM Normalizer: Version 3.2 Released!

Download it from the Visual Studio Gallery.

Enhancements in Version 3.2

Support for SQL Server Analysis Services 2016 General Availability (GA)


Command-line interface supports Visual Studio projects as source/target

Despite Visual Studio not being loaded (or required) in command-line mode, projects can now act as the source/target for comparisons (in addition to databases).

This is useful for automated builds, which get the latest version of files from source control.

The project path is stored in the BSMN file. It can be changed by editing the file.

<ComparisonInfo xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <ConnectionInfoSource>
    <UseProject>true</UseProject>
    <ServerName>localhost</ServerName>
    <DatabaseName>Tabular1200_wade_21527ea8-74fd-4bb6-b2e2-3d1cd3f70063</DatabaseName>
    <ProjectName>Tabular1200</ProjectName>
    <ProjectFile>C:\Users\wade\Documents\Visual Studio 2015\Projects\TabularProject1\TabularProject1.smproj</ProjectFile>
  </ConnectionInfoSource>
  ...

Support for Visual Studio configuration manager

Default values for the target server and database are based on the selected source project’s deployment properties, and the current Visual Studio configuration. Selecting a different source project (or re-selecting the current one) resets the defaults.

VSConfigurations