what is the best practice for design of large dimension, such as Order? In my scenario users want to analyze order intake using order status, issuer name and couple of other attributes, possibly even order number. We use fact dimension to accomplish that. Everything works, but I'm a bit concerned about performance. There are more than 10mil members in that dimension (and there is also invoicing dim as well, about the same size).
Is this the best design for this scenario? What if I create separate dimensions Issuer, Order Status ... and link them directly to the fact? Will the performance (though it's not bad now, I'm just thinking ahead) improve, and, most importantly, WHY? :)
Thanks.
Radim
What are your concerns about dimension performance?
You got to quite specific when you talk about performance. What is schenario for using your dimensions?
Do you expect users to drill down to the lowest level? Do you have nice natural hierarhies stucture into your dimension?
Analysis Services can nandle your multiple large dimensions. See referece to Project Real implemenation http://www.microsoft.com/sql/solutions/bi/projectreal.mspx
Building navigation paths using right set of native hierarchies is key to the dimension performance.
Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
No comments:
Post a Comment