SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Designing a Dim table for SSAS and SSRS


Designing a Dim table for SSAS and SSRS

Author
Message
adams.squared
adams.squared
Mr or Mrs. 500
Mr or Mrs. 500 (527 reputation)Mr or Mrs. 500 (527 reputation)Mr or Mrs. 500 (527 reputation)Mr or Mrs. 500 (527 reputation)Mr or Mrs. 500 (527 reputation)Mr or Mrs. 500 (527 reputation)Mr or Mrs. 500 (527 reputation)Mr or Mrs. 500 (527 reputation)

Group: General Forum Members
Points: 527 Visits: 441
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
RonKyle
RonKyle
SSCertifiable
SSCertifiable (6.9K reputation)SSCertifiable (6.9K reputation)SSCertifiable (6.9K reputation)SSCertifiable (6.9K reputation)SSCertifiable (6.9K reputation)SSCertifiable (6.9K reputation)SSCertifiable (6.9K reputation)SSCertifiable (6.9K reputation)

Group: General Forum Members
Points: 6926 Visits: 3620
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.



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search