dbTalk Databases Forums  

filtered dimensions

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss filtered dimensions in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
JamieBeerbower
 
Posts: n/a

Default filtered dimensions - 11-09-2004 , 07:39 AM






Hi all,
I'm trying to create a dimension in the analysis services based on only part
of the base table.
e.g. my base table has fields
criteria_id int && FK corresponding to gender, age category income category
etc.
value_id int && criteria_id + value_id form unique key.
text char && e.g. Male

with data
criteria_id value_id text
1 1 male
1 2 female
2 1 Age 10-20
2 2 Age 21-30
2 3 Age 31-40

I would like to create a dimension AgeCategory that only has the elements
from my base table with criteria_id 2.

I've tried setting the "Source Table Filter" in the advanced properties of
the dimesion editor. This looks fine in the data views but the source table
filter is not included in the initial join when I process a cube using the
dimension.

I could make a unique key rather than a compound key but wouldn't that
result in many unnecessary NULL elements?

I could break my table down into a set of count(criteria_id) tables in the
warehouse but that would be work and would reduce maintainability.

Can anyone tell me whether what I want to do is doable or what I'm doing
wrong?

Thanks
Jamie Beerbower



Reply With Quote
  #2  
Old   
Brian Altmann
 
Posts: n/a

Default RE: filtered dimensions - 11-09-2004 , 08:09 AM






You could create a view of your base table and use it as the source for your
dimension.
HTH,
Brian
www.geocities.com/brianaltmann/olap.html

"JamieBeerbower" wrote:

Quote:
Hi all,
I'm trying to create a dimension in the analysis services based on only part
of the base table.
e.g. my base table has fields
criteria_id int && FK corresponding to gender, age category income category
etc.
value_id int && criteria_id + value_id form unique key.
text char && e.g. Male

with data
criteria_id value_id text
1 1 male
1 2 female
2 1 Age 10-20
2 2 Age 21-30
2 3 Age 31-40

I would like to create a dimension AgeCategory that only has the elements
from my base table with criteria_id 2.

I've tried setting the "Source Table Filter" in the advanced properties of
the dimesion editor. This looks fine in the data views but the source table
filter is not included in the initial join when I process a cube using the
dimension.

I could make a unique key rather than a compound key but wouldn't that
result in many unnecessary NULL elements?

I could break my table down into a set of count(criteria_id) tables in the
warehouse but that would be work and would reduce maintainability.

Can anyone tell me whether what I want to do is doable or what I'm doing
wrong?

Thanks
Jamie Beerbower



Reply With Quote
  #3  
Old   
JamieBeerbower
 
Posts: n/a

Default RE: filtered dimensions - 11-09-2004 , 08:25 AM



Thanks for the idea...
Jamie Beerbower

"Brian Altmann" wrote:

Quote:
You could create a view of your base table and use it as the source for your
dimension.
HTH,
Brian
www.geocities.com/brianaltmann/olap.html

"JamieBeerbower" wrote:

Hi all,
I'm trying to create a dimension in the analysis services based on only part
of the base table.
e.g. my base table has fields
criteria_id int && FK corresponding to gender, age category income category
etc.
value_id int && criteria_id + value_id form unique key.
text char && e.g. Male

with data
criteria_id value_id text
1 1 male
1 2 female
2 1 Age 10-20
2 2 Age 21-30
2 3 Age 31-40

I would like to create a dimension AgeCategory that only has the elements
from my base table with criteria_id 2.

I've tried setting the "Source Table Filter" in the advanced properties of
the dimesion editor. This looks fine in the data views but the source table
filter is not included in the initial join when I process a cube using the
dimension.

I could make a unique key rather than a compound key but wouldn't that
result in many unnecessary NULL elements?

I could break my table down into a set of count(criteria_id) tables in the
warehouse but that would be work and would reduce maintainability.

Can anyone tell me whether what I want to do is doable or what I'm doing
wrong?

Thanks
Jamie Beerbower



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.