May 6, 2013 at 11:28 am
New to SSAS. I'm working on my first cube. I'm creating a dim table for the accounts. The level of detail that we would use for SSAS is the accounts county, but for SSRS we would want to be able to show the street address. We want to be able to use the dim tables for reporting out of SSRS as well as the cube. So if I add the street address to the Dim table, but I do not use it as an attribute in SSAS, is that considered a No-No in the SSAS world? Is there a major negative impact on the Cube if I do include the data in the table?
Thanks
May 7, 2013 at 6:51 am
There's not enough information here to give you a good suggestion for your case, particularly in terms of dimension record count. Here are some guidelines.
If you absolutely need it there as a business requirement, then you need it. Usually in the dimensions this is not an issue, unless it is a degenerate dimension. If the dimension has about the same number of rows as the fact table, it is probably degenerate.
Street addresses in the fact table are not automatically bad, but they are usually not good. If the fact table is millions of records, the presense of these long fields makes everything slower. Whether it is too slow is up to you and your users. Ideally the fact table consists of pointers to dimensions so that the rows are as small as possible. As long as the trade-off is understood, then do it. I personally prefer my operational reports requiring that detail to come from the operational database.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply