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!
Is there any way to automatically install the visual studio extension by copying the vsix file to one of the following directories:
%LocalAppData%\Microsoft\VisualStudio\<Visual Studio version>\Extensions\. or <Visual Studio installation folder>\Common7\IDE\Extensions\ ?
I tried doing that and restarting visual studio but it did not seem to automatically register the extension. Am I missing a step?
SSDT-BI is starting to be available for VS 2015: http://blogs.msdn.com/b/ssdt/archive/2015/10/27/sql-server-data-tools-preview-update-for-october-2015.aspx
Do you have plans to add support for this version of Visual Studio? If so, do you have a timeline in mind?
Barring unexpected issues, a tested version will be available soon after VS2015 hits RTM. As soon as we have any announcements, I'll make them publicly available immediately!
Love the tool, but I noticed that I had adjusted a CASE statement in the table's partition/definition and BISM Normalizer didn't catch the change in the compare tool for tabular.
Is that a feature that will be added in the future or should the tool have seen there was a different in the TSQL behind the table's definition?
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 firstname.lastname@example.org 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?