Hi All,

We are facing some problems with Snow Flake schema in AS 2005,

Problem with SNOW FLAKE Schema in AS2005
Example Schema : 2 Dim Table and 1 Fact Table

DIM TABLE 1
-------------------
Region ID
Region Name


DIM TABLE 2
---------------
User ID
User Name
Region ID

FACT TABLE
--------------------
User ID

RelationShip
------------------

FactTestData --------->DimUser---------------->DimRegion

The above is a very simple Snow Flake Schema the FactTestData is directly
related to the Dimension DimUser and DimUser is directly related to
DimRegion;

The FactTestData is related to DimRegion through DimUser.


Now the problem is when a report is created in reporting services, the
measure (Fact Test Data Count) is dragged and dropped in the query builder,
now if I apply a filter

DimUser.iRegionID = 1 it works, but when we drag and drop the filter from
DimRegion.iRegionID = 1 it does not filter, similarly if the column Region ID
is dragged and dropped from DimUser then the result set (measure count)
breaks up according to regions, but when the Region ID is dragged and dropped
from
Dim Region it does not break up and shows the same number for all regions.

In other words the filters and columns works perfectly if the dimension is
directly related to the fact, is there solution for the same.


Thanks
Balaji

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums...-olap/200607/1

In the "Dimension Usage" tab, make sure the DimRegion is related to the
measure groups.

If they arent related, the slicing will not work.

balajikkrishnan via SQLMonster.com wrote:

Hi Rose,

They are related, but still it dosent work.

Balaji

Rose wrote:
--
Message posted via http://www.sqlmonster.com

I had similar problems before. In your example, after I created a
hierarchy in DimUser that looks like this (Let's call this
UserRegionHierarchy) :

RegionID

basically, any RegionID that I need, I would use

[DimUser].[UserRegionHierarchy].[RegionID].&[1]


and I did not need the DimRegion anymore.

Not sure if this helps.


balajikkrishnan via SQLMonster.com wrote: