You’re offline. This is a read only version of the page.
10
I have recently expanded a number of OLAP cubes for a customer. During the project it was discovered that adding ENUM attributes to the Dimension data (for example by adding ENUM fields to SalesLineExpanded and configuring them as Attributes in SSAS) would result in nested CROSS JOIN statements in the SQL constructed for the _DIM table in the DSV.
After 13 CROSS JOIN statements the dimension data is ... obviously ... blown out of this world, resulting in a massive 35 million rows from which most is absolute garbage. As CROSS JOIN statements produce a Cartesian product, this means that the solution breaks, or is cluttered with garbage, whenever the ENUM fields go beyond 4 or 5.
We are currently considering manual fixes to the SQL in the DSV (which will require constant re-patching for every new deployment) or to convert all ENUM fields in the views with calculate String columns (which will then not be language independant).
Any fixes to this issue is appreciated.
AX 2012 R2 CU7 (6.2.1000.4051)
SQL Server 2012 R2 Enterprise edit.
*This post is locked for comments
I have the same question (0)
Share
Report
All responses (
Answers (
