August 20, 2014 Leave a comment
As I have said for (almost) 3 years, the use cases for BISM Normalizer are more than just helping migrate from Power Pivot to SSAS. Apart from merging code bases, and deployment of large, partitioned tabular models, etc., I probably have not emphasized the ease of deployment through dev, test, prod environments from Visual Studio. Let’s be honest; while they may not admit it, I suspect a large proportion of projects deploy from Visual Studio using right click > Deploy in Solution Explorer.
BISM Normalizer allows piecemeal deployment of individual features through environments from Visual Studio, which is valuable for many projects. Right click > Deploy in Solution Explorer obviously doesn’t achieve this. Apart from being an all-or-nothing deployment technique, it doesn’t take the state of each environment into account.
For example, BISM Normalizer makes it possible to pick limited particular features that have been signed off in a user-acceptance-testing environment and deploy to production – even if the SSAS objects required have been modified in the lower environments.
Benefit: easy deployment that is more responsive to the customer.