Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 Analysis Server and Reporting Services (2008)
 Problem with a product dimension

Author  Topic 

deltalima
Starting Member

1 Post

Posted - 2011-05-17 : 15:21:39
Hi guys, I would like to know if you can help me with this issue:

I'm building a Datamart in SSAS 2005. This is one of my firsts ones... For achieve that, I'm attempting to build a dimension of products, based on credit cards, debit cards, insurances and saving accounts.

For that, I have a table with the following estructure:

BinNumber (Primary Key, Unique)
BinDescription (Name of the bin number)
Brand (Visa/Mastercard/Others)
SubBrand (Classic, Gold, Platinum, Signature, etc)
Segment
ProductCategory (Credit Card, Debit Card, Insurance, etc...)
Program.

I manually designed the dimension, considering BinNumber as the key column, and BinDescription as the column containing the member name.

My hierarchy should be as the following:

Program
ProductCategory
Segment
Brand
SubBrand
BinDescription

And the problem appears at this moment: When I browse the dimension data, It shows me the data absolutely messed up. I mean, It shows me, for example, BinDescriptions that don't belong to an specific SubBrand, or Brand. And in the same way with the all levels of the hierarchy.

What could I do in this case? Is there any property I'd consider???

Thank you a lot for your help



Daniel Leon
BI Developer Analyst
Lima - Peru

nigelrivett
Master Smack Fu Yak Hacker

3385 Posts

Posted - 2011-05-18 : 06:04:45
First of all - can you use v2008 instead?

To be a hierarchy your dimension should not have the same BinDescription for two different SubBrands - and the same applies to each level and sub level of the hierarchy.
You can get around this by using the key column as a concatenation of the column + columns for all levels above but it probably means that you don't really have a hierarchy and should look at the data.


==========================================
Cursors are useful if you don't know sql.
SSIS can be used in a similar way.
Beer is not cold and it isn't fizzy.
Go to Top of Page
   

- Advertisement -