(I'm also going to post this in SSAS, as I'm not sure if this is an SSIS or an SSAS issue.)Hello, I have a cube, and its data population for Dimensions is driven by values obtained from the Tabular Module Partitions. System: SSQL 2014, VS13Cubes been running fine, needed to add dimension to cube, could not see in the SSIS packages a traditional place to add, like in my other cubes which don't use ForLoop Containers with tasks that run through the Partition tables to update the Dimensions as this one does, they are just straight SSIS packages that interact with the source view which I have successfully modified. So I determined to add the new dimensions as columns in the Cubes model only, on the target partition, via table Properties, etc on the grid, and went to the diagram and went to the table, and moved it to the appropriate hierarchy.I saved, deployed, and then re-ran the cube, and it failed. Fails on the last step, which is a Parititions Process Partitions step (but in stepping through, also fails on most all the partitions tasks including one the deals with dimensions)I've stepped through everything, tried lots of things, ended up restoring back to the way it was, and it still fails on the The issue seems to be in the SSIS Package, that deals with the partition tables, and somehow to simply add a dimension to the model has caused the SSIS packaged that interact with the cubes partition tables is out of whack, even when reversed.Can someone please help me address this? These Tabular Partitions Module tables are more than a little tricky. Please let me know what additional details I can share.Thanks,JPQ
↧