Comparing a SSAS project (dwproj) to a database running on a server, dimensions having the same name are not put one beside the other, but many are on their own line without the dimension form the other side, which then appears a few lines below or above, on its own as well.

Thank you for the powerful tool , It would be better if the comparing was between two XMLA cubes to make the changes permanent.

Similar to other ideas on this forum, but applying it at a general level, it would be great to choose only those properties/elements that are relevant for comparison. For example, when comparing an AS project file to a database deployment, a difference is shown for defaults for ProactiveCaching, Language, and Collation. In the project, these values may be blank, but in the database, the defaults have been applied implicitly upon deployment. The ability to ignore these properties would prevent these false positives.

Love the tool, thanks!

I have a MDX security expression in a Role for a specific dimension attribute that I had to change. The tool did not detect that change...at least I can't find it. It wasn't listed in the Role category, nor was it listed in the Dimension itself.

It would be nice if the tool would highlight the differences without having to drill into each major section.

Unless I am using the tool wrong, it appears that the "=" sign is obviously no change detected. But a checkbox makes me thing that there ARE differences detected. But I am having trouble locating the differences. Highlighting in a configurable color would be nice.

Awesome tool by the way!

Would be great if rather than doing a process default on the database it only scripted the processing of objects impacted by the change script.

It would be really cool if there was a checkbox that would hide all objects elements and properties that didn't change so that only the ones that are different show. For QA purposes, this would make it fast and easy to identify the changes without having to navigate the entire structure.

But as I said before...

This is an awesome tool!

Often times we will process data and then sync to the Query server, it would be nice to see that that partition sizes are match (or at least close) before syncing.

Sorry if it's in the beta and I just missed it, but I don't see any SCM integration in the SSAS Compare beta. I would like to be able to version my deployment scripts without manual intervention, much as you do now with SQL Compare and SQL Source Control.

Currently you can only synchronise entire measure groups and entire dimensions. More granular control is required: the ability to synchronise individual measures, dimension attributes, member properties and relationships.

should be able to connect the ssas through the web service (ex: http://xxx.xxx.xxx.xxx/olap/msmdpump.dll)

When changing the null processing option on a key column from Default to Unknown the compare didn't pick the change up.

Comparing and reporting differencies in every calculated member or scope would help to have better control during deployment.

BTW: I cannot see highlighting in 0.1.0.436

I have a staging cube that I deploy to from BIDS, then I use SSAS compare to update my development/qa/production cubes. I see expected changes in my staging cube for a named query change but SSAS is not picking up these changes and pushing them forward to the new cubes.

I am Seeing lots of differneces come up because Language = 2057 on one of our mahcines and Lnguage = 1033 on another. I think someone has rebuilt the SSAS project form a badly configured server and not set UK English. They have subsequently deployed this version an hence the differences. This seems to be pretty much the only difference cropping up on the comparison I'm running today.

The biggest bottleneck to parallel dev on SSAS is the DSV. The curent tool does a great job of highlighting differeces in DSVs but its an all or nothing replace. When two versions have both progressed being able to selectively merge the DSV portions into a single model would be an amazingly useful tool for BI teams. I appreciate this is hard and not really supported in XAML but a metod of merging DSV's or some way of extracting and merging the competing XAML sub elements would be really useful.

Different environments (DEV, TEST, UAT, Live Support, live) often have different data sets so being able to ignore differing partitions within the projects would be useful. Though the ability to align the query used within the partitions would of course be very useful

Add support for comparing and scripting the Tabular Model in SSAS

often I am deploying the same cube to multiple cubes with the data source always varying as the underlying warehouse is different. I would need to either by default leave the data source connection string left out or have the ability to review it before executing the script.

Added data compare functionality - Many times we are making changes that have to be manually verified. This would automate that