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!
Great solution, loving the support for BIDS helper tabular objects but I have come across an error. I added an action to my solution then tried to deploy it but an error message "No room is available to display rows" appears when I validate selection. I have removed the action as well as reinstalled BISM Normalizer but the error still appears. Do you know may have caused this
Thank you for the feedback, and sorry to hear you are getting an error.
I would love to recreate the error and fix it. Might you be able to e-mail me the project files at firstname.lastname@example.org ?
Hi dear Christian,
First of all I wanna thanks for you developed this wonderful tool.
We are using the BIDS Helper for creating Translations, Display Folders, Actions and other good things in Tabular models like Multidimensional OLAP cubes.
But when we create above items with BIDS Helper in a model1, BISM Normalizer doesn't compare and commit changes to model2 about the translations,actions, etc. added to the bism file by BIDS Helper.
Could please add this features compare and commit functionality to BISM Normalizer.
you can find detailed information BIDS Helper (http://bidshelper.codeplex.com/)
We have been using BISM Normalizer to generate change scripts used during a release. However, we have to manually change the connection string in the script. It would be nice to have an option to preserve the target's connection strings.
Thanks again and Happy Birthday (to BISM Normalizer)
You should be able to Skip the difference for the connection string in the differences grid (by default it should have "Different Definitions" status and an Update action item - which can be changed to a Skip action item).
Does this work for you? Or are you generating a single script for multiple environments that each have different connection strings?
First of all thank you Christian for this amazing Extension.
I seem to have found a minor bug in the Normalizer. When you change a specific column format (example: Date column format) the normalizer does not detect any model changes and does not deploy.
Can you confirm this and possibly make a fix for it?
Thank you :)
Thank you for the feedback.
You are right that it does not currently include column formats in column definitions (and therefore does not detect changes in format). It does include the datatype, but not the format.
I do plan to add the format to column (and measure) definitions, but I probably won't get the time till January or February 2014.
I will post on my blog when I get this done.
thanks for the great tool. it does however seem that it does not sync Perspectives? I ran it a couple times but in the end had to deploy using Deployment Wizard, and then only did Excel pick up the new perspective.
Hi - yes it does work for perspectives. You need to click on the options button in the connections dialog (where you specify source/target databases/projects) and ensure the perspective options are selected. This should work fine and you should see the perspectives listed in the differences grid. Let me know if you have issues.
We have been using the app for a while now and suddenly we getting a message on one of our models saying: "Could not read workspace setting file..." We have tried opening and closing the model and even visual studio, but still receive the message. I can even deploy the model without issue.
Can you try creating a new settings file? To do this, create a copy of the whole project folder, show hidden files, delete the settings file(s), reopen the project and the bim file in Visual Studio. Alberto Ferrari does it here (for a different reason): http://sqlblog.com/blogs/alberto_ferrari/archive/2011/09/27/creating-a-copy-of-a-bism-tabular-project.aspx
If this works, can you send me an e-mail at email@example.com telling me filenames of both the old and new settings files?
we are trying out a merge of 2 projects, but the compare wont work as it thinks that the ID of the database contains special characters. I have confirmed that the database ID in the asdatabase file doesn't contain any of the blacklisted characters, it only contains underscores.
Can you help?
I would like to reproduce this problem. Any chance I could get a copy of the project files? Alternatively (if sensitive models), is it possible to recreate in dummy projects?
If you want to take this offline, or e-mail me a copy of the files, my e-mail address is firstname.lastname@example.org
A few of you have had issues with the installation machine pointing at a remote addin folder. Here are some workarounds.
1. If you can run the installer, set it to a local addin folder. If necessary, you can configure the local Addin folder in Visual Studio options.
2. If you cannot run the installer at all because it "could not access the remote network location", send me an e-mail at email@example.com and I can send you the files to manually place in a local addin folder.
3. As discovered by Jonas Edsman, after manually copying the files if you still get error 80131515 when Visual Studio tries to load even from a local addin folder, then set "<loadFromRemoteSources enabled="true"/>" in devenv.exe.config
Thanks for the tip Jonas!
I'm very impressed by your tool in a development environment.
At the moment I'm trying to compare a development tabular model with a model that is in an QA environment. I'm a member of the Administrators role (Full control), but I'm unable to compare the O model to the QA model. This is the error:
The 'Role' with 'ID' = 'Administrator' doesn't exist in the collection.
Could you enlighten me? :)
I have made a change (version 18.104.22.168) to the way it checks whether the current user is a member of the Analysis Services administrator group (right-click server in Management Studio > Properties > Security). Give it a go, and let me know!
A colleague has pointed out that on the description page it says the software will expire on 30th June 2013 and it is not clear what will happen then?
Please say it will continue past then!
Andrew - I have no intention of charging license fees. I have no plans to disallow access to BISM Normalizer. The reason there is an expiry date is just to protect my IP - for example if I ever receive an offer I can't refuse for the source code.