SSAS Designer showing empty phantom/duplicate tables
Working with an SSAS multidimensional cube that was developed using SSDT 17.3, the Data Source View for the cube is showing multiple phantom tables as the data source view is changed/refreshed. This is happening when looking at the Data Source View for both cubes as well as dimensions.
The Data Source View object itself does not show any issues, cube functionality does not appear to be affected when it is deployed and processed.
When trying to use the "Copy Diagram from" function, Visual Studio crashes on me.
The issue has persisted as I've upgraded to 17.4, as well as testing with SSDT 15.x. This is a continuation of the issue described at https://social.msdn.microsoft.com/Forums/en-US/b4be5ff0-5b9f-4538-9ec0-5def3bab4fff/phantom-tables-in-ssas-cube-data-source-view?forum=ssdt
D Smulders commented
Actually this issue is a bigger problem than you all think. Also, it's not in SSDT.
The issue is originating in BIDS Helper (or whatever it is called nowadays). I've had this on several projects now and every time the full project went from bad to worse.
Sure I've found ways to edit the XML to remove the visual issue, however, there is an underlying problem that is much worse: it's an issue with the aggregation design storage and it will double, triple, etc etc the storage needs for any aggregation a member of a ghosted table that is included in that particular aggregation.
These aggregation files are -not- XML but a binary storage, so they are not easily changed. BIDS Helper has a component to edit those... but that component is obviously faulty.
So yeah, I don't mind the visually ghosted tables, but I do mind the aggregation desings corrupted. A 1 hour / 10 GB cube easily went to 3 full days of processing and a couple of terabytes of storage within a week. Depending which dimensions or facts where altered by the development team.
The only solution I have found is scrubbing the full SSDT solution including BIDS Helper off all developers disks, re-install SSDT, and then manually re-build the whole corrupted cube projects by hand as well.
I am a 100% sure it's BIDS Helper. It took me 3 corrupt projects with different clients to figure out what the linking factor throughout those projects was (and 4 projects where we didnt use BIDS Helper). Then I've thoroughly tested with multiple re-installs and PC's to replay the issue. They only emerge from PC's infected with BIDS Helper.
Shame, because BIDS helper is quite a useful tool. I do miss their functionality. I've notified them 2 years ago, but as far as I know only the visual aspect is somewhat better, but the aggregation corruption is still in there. I gave up hope so I don't monitor progress anymore with that software.
It is quite a big mistake. I found out that a duplicate fact table in the cube data source view is created always when you add a new measure from the same fact table. So as many measures you add from the same table as many duplicate tables you will get. After you save and close cube designer you will get only a blank frame with the same fact table name. The only way how to make a correct visual cube design is to use cube wizard but once you need to add anything to this layout you have no chance to make it correct. I wonder that nobody fixed this bug since 2015. It is the same with SSDT 2015.
Thank you for asking questions, If you want to Know About SSAS, please go through this link: https://mindmajix.com/ssas-training
Thanks & Regards,
"Solution" is the wrong word, it is a band aid, not a fix! Stupid we have to jump through hoops to make something work properly.
I have the same problem, very anoying. but there is aeasy way to fix it.
1.- Right click on the cube and go to view code (F7).
2.- Then on the first Annotation "DiagramLayout" delete all the <value> tag. you will have something like this.
3.- Comeback to the Cube design view.... and Magic.... everything looks ok now.. and if you comeback to the xml again, the <value> tag inside of DiagramLayout was recreated.
Same here on VS2015 SSDT: 14.0.61707.300 but it works in VS2017 SSDT: 15.1.61901.03220
In other hand the main DSV doe refresh from database in VS2015 but does not work in VS2017.
So we have both installed to be able to do 1 job. Not good at all Microsoft.
I see exactly same behaviour when adding new measures to an existing measure group. I tried both VS2017 and VS2015 same result, MS please look at this issue it's very confusing to work with.
This problem seems to have performance issues which needs to be fixed ASAP. Many thanks
VS version : VisualStudioVersion = 14.0.25420.1
László Kiss commented
Totally same on
Microsoft Visual Studio Professional 2015
Version 14.0.25424.00 Update 3
Microsoft .NET Framework
SQL Server Data Tools 14.0.60629.0
and 2 years old issue
OMG, same problem in VS 2017 SSDT version 15.8.6 it is really annoying.
Niels Mynster commented
Very annoying bug: after adding some measures, phantom tables appear and facttable contents are blank.
Cube remains working but the view is unreadable and becomes a mess with phantom tables and empty facttables :-(
I hope MS solves this asap.
Remco van Haaren commented
It is still there in Visual Studio 2017 SSDT version 15.7.3
Filip Sirucek commented
I found out that duplicate fact table is always created after you add a new measure from the same fact table in the cube data source view. So many measures you add from the same table so many duplicate tables you will get. After you save and close cube designer the images of duplicate tables changes into blank frames with the same fact table name. There is no way how to get rid of these duplicate tables. When you need to move table or arrange the design you will see the duplicates hidden under the original fact table. Such a design is confusing and unusable.The only way how to make correct visual cube desing is to use cube wizard but once you need to add anything to this layout you have no chance to make it correct. I wonder why nobody have fixed this bug since 2015. This bug occurs in SSDT 2015 and also in 2017. Please fix this bug as soon as posiible. Thank you.
This error/bug in SSAS makes the Cube data source view unusable. We need a fix for this issue ASAP.
Evan Morgoch commented
Looking at the raw XML view in my cube, it looks like all the empty tables are a result of the multiple copies extra <ddscontrol> objects being added. An example of the full control is:
<ddscontrol controlprogid="DdsShapes.DdsObjectManagedBridge.3" tooltip="MyTable" left="-83279" top="-15143" logicalid="230" controlid="1" masterid="0" hint1="0" hint2="0" width="6376" height="5000" noresize="0" nomove="0" nodefaultattachpoints="0" autodrag="1" usedefaultiddshape="1" selectable="1" showselectionhandles="1" allownudging="1" isannotation="0" dontautolayout="0" groupcollapsed="0" tabstop="1" visible="1" snaptogrid="0">
<ddsxmlobjectstreaminitwrapper binary="000c0000e818000088130000" />
<shape groupshapeid="0" groupnode="0" />
The difference between these vs. a "real" one is that the <ddsxmlobj> tag is fully flushed out (ie. <ddsxmlobj>
<property name="LogicalObject" value="dbo_factOE" vartype="8" />
In my one dimension, I was able to "fix" it by manually removing all the trouble <ddscontrol> objects. However, trying to do the same in my cube caused it to crash. Presumably because there were also relationship lines in the cube that were pointing to those empty tables that were removed, rather than pointing to the real tables.
Community 2017, version 15.7.5, has similar issues with tables that are completely blacked out in the Cube Structure view.