We finally put into production a feasible solution. Sorry deepak and dxd, I
had to ditch the excellent ideas that you put forth previously using the
Patient ID as a dimension. It was just too big for the hardware to handle.
So we went for a multiple drillthrough solution which is working fine so
far. Keeping my fingers crossed!!
Thanks guys!! If anyone needs further info on my solution please feel free..
Chumma Dede
"Acquiesce" <member25254 (AT) dbforums (DOT) com> wrote
Quote:
What will the performance like if you create such a MDX? What isyour
total number of records? I've tried the NonEmptyJoins and my ID
dimension goes way above 200K and its slowing down the performance of
the front end query. Do let us know the performance once you intergrate
the 3 cubes and MDX together!
Cheers
--
Posted via http://dbforums.com |