I am looking for a best practice with respect to create a Dimension for General Ledger. In my opinion this Dimension is a 1 to 1 copy of fact General Ledger since the user would like to see all attribute values of that Fact.
And there lies my problem because if I create this Dimension, the dimension holds the same amount of records of the fact General Ledger what makes it so slow to load.
Any input of best practices is very much appreciated.
-Miracles are easy, the impossible takes a bit longer-
If I understand correctly, the dimension is one to one relationship copy of fact table, so the dimension holds large members in it which cause the performance issue. Now you are looking the best practices to handle large dimensions, right? If I have anything
misunderstood, please point it out.
In this case, here is blog which describe some tips about handle large dimensions that might helpful for you, please refer to the link below. Tips: Processing Large Dimensions
If you have any feedback on our support, please click
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.