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!
My copy of BISM normaliser has expired, the message tells me the last day is 2014-06-30, I’ve uninstalled and downloaded the most recent version but I’m still getting that error, the version I Am running is 1.3.13. Is there a later version?
Version 1.3.13 should run till end of 2014. Please check the Visual Studio About box. It will have an item for BISM Normalizer (at bottom of list of installed extensions) that shows the version number. If that doesn't work, we can keep investigating.
So in the project, we had a few partition for the fact to start out. After it's in production, we have a separate process to dynamically create new partition daily and process that only (due to large amount of data daily).
Historically, using BISM, and not select "include partition" in comparison servers us extremely well when we try to deploy minor changes to cube, such as attribute name change, new attribute in existing dimension, etc.
However, when we need to add new dimension, thus new relationship between the fact and a few new table/dimension, it doesn't work anymore.
Even with ignoring partition, when I deploy the new dimension to production, BISM normalizer would still wipe away all the dynamically created partitions in fact table, thus basically erasing months of data. :( Luckily we took a backup beforehand
We had a couple workaround in mind, but would be really great if it still retains the dynamic partitions even when we are deploying new dimensions.
Thanks for the question.
BISM Normalizer retains partitions only if the table action is "Skip". An "Update" action performs a full update from the source definition (including partitions). Technically, an Update replaces the target table definition with a clone from the source. Same applies to other "first-class" objects - i.e. that have their own node in the differences grid. Partitions do not, because they are part of table definitions.
The "include partitions in table definitions" checkbox in the Options dialog affects only the comparison process, not the update process.
When I have previously had to make changes to existing tables that have partitions managed by the ETL ("dynamic partitions"), I have allowed for the time to fully rebuild and reprocess partitions. Changes such as adding a new column require all partitions to be reprocessed anyway before it is usable.
One more thing, if you are saying that a new definition of the dimension table wipes out the fact table (different table) without any structural changes to the fact table, then that should not happen - unless again, the fact table definition changes - like adding a new column (e.g. foreign key column to the new dim table).
If you are saying the fact table has an action item of Skip and still it's partitions are being wiped out, then please e-mail me on email@example.com for further offline investigation.
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!