This is a brilliant utility! You just saved me hours of manual, tedious changes to merge two cubes. And you found several changes that I would have overlooked. Microsoft should buy this from you to include in the base product. Thanks for making this available!
i don't write reviews usually.. but this is AMAZING!!! we've developed scripts to do automatic partitions on our tabular cubes, so redeploying changes from the SSDT project is a NO NO, as it erases my existing partitions all the time.
Using BISM normalizer gives me the confident to make metadata / structural changes to our server, without worrying that it would accidentally overwrite other stuff, such as my auto created partitions, and I can review the xmla scripts before I run it.
i seriously won't know what to do if it were not for bism normalizers
p.s. also i was just cursing my life when i couldn't get the BIDS helper actions deployed to my prod (and I don't want to do deploy from SSDT), come here, and found out that the new version now supports it! amazing!
Can you please share your roadmap for upcoming release(s)? We've noticed that the last version was published back in January. We would like to get a sense of what may be coming next and approximately when.
The top 4 items (in order of priority) on the backlog right now are:
- Assess SQL 2016 compatibility
- Remove requirement to be SSAS admin
- Model processing options upon deployment
- Switch source/target connections in connections dialog
Don't have an answer currently regarding timeline.
Feature suggestion: add a filter to show only objects that have different definitions, are missing in source or are missing in target. This will make it much easier to focus on the differences, as the majority of the objects are normally equal.
The feature can work similarly to the "Show Equal Objects" filter in the SSDT Schema Comparison window.
Would it be possible to enhance the tool so it supports default measures?
We are currently using the approach at this link to manually apply the measure to the XMLA script: http://www.sqlservergeeks.com/sql-server-analysis-services-assign-a-default-measure-in-ssas-tabular-model-solution/
BISM Normalizer is giving us the following error message when pushing a change to our tabular model:
"Cannot query internal supporting structures for column 'Table_X'[RowNumber] because they are not processed. Please refresh or recalculate the table 'Table_X'."
We can't seem to get past this error. Have you seen this before?
It looks like you have deployed some changes that require reprocessing a table in the target model. Currently BISM Normalizer doesn't have functionality to do processing as part of the deployment. It needs to be done in Management Studio, or using whatever mechanism you have for processing.
I actually have it as a feature I would like to add in the future - to do processing as part of the deployment from BISM Normalizer - but it is not in the product yet.
It's been great using the BISM Normalizer, thanks for developing this tool.
I need your help as I have recently come across an issue with the BISM Normalizer where I get the following error when I click the "Validate Selection" button:
No room is available to display rows.
I have installed the latest version, 18.104.22.168, but that didn't solve the problem. I work with 2 other colleagues on this project and they are not hitting this error so I'm wondering if it's something with my workspace database. Any leads you can provide would be very much appreciated.
At least one other user has had the same problem, but I have been unable to reproduce it. If the same tabular project works on your colleagues' machines, it may be something environmental to do with your machine set up.
If you like, I can set up a Webex for you to show me reproducing the error - just in case something comes up. If so, e-mail me at email@example.com and I'll set it up. Obviously I'd like to reproduce it, but it is proving a tricky one to reproduce!
Hi Prafulla - I have still not been able to reproduce this. I will be making some big changes to a release in a few weeks. If you still have this problem with the new release, maybe we can webex for me to see.
I'm getting the following error message when doing a "Validate Selection":
Another 'DatabasePermission' object has the 'DatabasePermission 2' name
Any idea what this is about?
I have installed BISM Normalizer 22.214.171.124 on VS2012 SP4. However, I find that it do not load. After looking at the ActivityLog, it seems require VS2013 assembly to work:
<description>End package load [BismNormalizerPackage]</description>
<hr>80004005 - E_FAIL</hr>
<errorinfo>Could not load file or assembly 'Microsoft.VisualStudio.Shell.12.0, Version=126.96.36.199, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.</errorinfo>
So I install VS2013 isolated shell, and then I can load the application. But When I start compare the model. The same error popped up again:
Could not load file or assembly 'Microsoft.AnalysisServices, Version=188.8.131.52, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
I'm quite upset that my beloved tool does not work on VS2012, but unfortunately My company has not upgraded to VS2013 yet.
Is there any solution to resolve?
I tried to get the already modeled structure from a deployed project into an empty one. The idea behin it is to use the modeled hierarchies etc. and get them into a new model. Next step would be to add a new fact and build the relationships.
The only thing that worked for me was getting all content of the model into my new one and then delete what I did not need any more. Every other option I tried like selecting only the connection and one table (skip the rest) did not succeed.
Am I doing things wrong or is this just a use case BISM normalizer is not meant to handle.
BISM Normalizer should work well for your requirement. Do you want to do a Webex so you can show me the process you are following? If so, e-mail me at firstname.lastname@example.org and I'll set something up.
thank you for your support. During the Webex we installed the latest version and everything worked as expected. Problem was the same as in the topic below the existence of measures with ']' in their names.
if the name of a measure contains '[' or/and ']' the name is cut off in the Diff-Viewer window
Also the wrong definition seems to be derived from online databases in this case
maybe a similar issues exists for other special characters too?
Version 184.108.40.206 deals with the ']' character (with a caveat - read below). I did some digging ...
Before SP1, no special characters were even allowed in measure names.
Since SP1, special characters are allowed. However, if you open the .bim file and look at the XMLA for the command text in the MdxScript elements, you will see that Microsoft does a replacement of ']]' with ']' when displaying in the tabular model designer (genius). I'm assuming they have some code that depends on ']]' to parse measure names and know when the end of the measure name occurs.
I have built similar logic to allow BISM Normalizer to work with ']' characters, but I have not gone to the trouble of displaying ']]' as ']'. It should update/create measures in the target database without problems and they will appear the same as in the source model in the tabular model designer, but in the BISM Normalizer differences grid, they show as ']]'.
Maybe at a later date, I will change it to show as ']'. We'll see.
Thanks for pointing this out.