Check the settings of Member Keys Unique and Member Names Unique properties
in the advanced tab on the level. If this doesn't work, what error are you
seeing during processing?

- Matt Carroll
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Eugene" <shieug123@yahoo.com> wrote in message
news:da0b8ea2.0307220810.554520ea@posting.google.c om...
> Hi,
>
>
> I run into the problem when I learn and practice the dimensional
> modeling. I try to use snowflake schema and my secondary dimentional
> tables (those dimentional tables link to the first level dimensional
> tables but not directly link to the fact table) have many-to-many
> relasionship with the first level dimentional tables, so I have to use
> a link table between those relasionship, but when I do so, the
> processing failed in SQL Server OLAP environment.
>
> Am I doing something wrong here? Or what should be the correct way to
> do that?
>
> Thanks in advance for all the help!
>
>
> Eugene

You might also try creating what look like pure star schema views on top of
your snowflakes.

----------------------------------------------------
The views expressed here are my own
and not of my employer.
----------------------------------------------------
"Matt Carroll [MS]" <MattCar@online.microsoft.com> wrote in message
news:OXc7sXHUDHA.2316@tk2msftngp13.phx.gbl...
> Check the settings of Member Keys Unique and Member Names Unique
properties
> in the advanced tab on the level. If this doesn't work, what error are
you
> seeing during processing?
>
> - Matt Carroll
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Eugene" <shieug123@yahoo.com> wrote in message
> news:da0b8ea2.0307220810.554520ea@posting.google.c om...
> > Hi,
> >
> >
> > I run into the problem when I learn and practice the dimensional
> > modeling. I try to use snowflake schema and my secondary dimentional
> > tables (those dimentional tables link to the first level dimensional
> > tables but not directly link to the fact table) have many-to-many
> > relasionship with the first level dimentional tables, so I have to use
> > a link table between those relasionship, but when I do so, the
> > processing failed in SQL Server OLAP environment.
> >
> > Am I doing something wrong here? Or what should be the correct way to
> > do that?
> >
> > Thanks in advance for all the help!
> >
> >
> > Eugene
>
>

Hi, Matt,


The message is still"Unable to brouse to dimension'New Dimesion'. The
dimension cannot be displayed until a cube that contains it has been
processed", even after I checked the "ordering & uniqueness of
members" option in the select advanced option window.

Kevin,

Say, I have a employee dimension for some fact table. Link to the
employee dimension, say I has a secondary dimension called:
officebuilding, which I have to model it as many-to-many to the
employee dimension, so I have to have a link table called: emp_office
table. I don't know how can I build a view to avoid them.

Thanks so much for all the inputs.


Eugene

"Kevin" <ReplyTo@Newsgroups.only> wrote in message news:<#koLisIUDHA.940@TK2MSFTNGP11.phx.gbl>...
> You might also try creating what look like pure star schema views on top of
> your snowflakes.
>
> ----------------------------------------------------
> The views expressed here are my own
> and not of my employer.
> ----------------------------------------------------
> "Matt Carroll [MS]" <MattCar@online.microsoft.com> wrote in message
> news:OXc7sXHUDHA.2316@tk2msftngp13.phx.gbl...
> > Check the settings of Member Keys Unique and Member Names Unique
> properties
> > in the advanced tab on the level. If this doesn't work, what error are
> you
> > seeing during processing?
> >
> > - Matt Carroll
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "Eugene" <shieug123@yahoo.com> wrote in message
> > news:da0b8ea2.0307220810.554520ea@posting.google.c om...
> > > Hi,
> > >
> > >
> > > I run into the problem when I learn and practice the dimensional
> > > modeling. I try to use snowflake schema and my secondary dimentional
> > > tables (those dimentional tables link to the first level dimensional
> > > tables but not directly link to the fact table) have many-to-many
> > > relasionship with the first level dimentional tables, so I have to use
> > > a link table between those relasionship, but when I do so, the
> > > processing failed in SQL Server OLAP environment.
> > >
> > > Am I doing something wrong here? Or what should be the correct way to
> > > do that?
> > >
> > > Thanks in advance for all the help!
> > >
> > >
> > > Eugene
> >
> >

This message means that the AS UI is not able to simulate the data contained
in the dimension using a local cube. This may be because the estimated size
of the dimension is large or possibly because it uses a feature not
supported in local cubes. If you process a cube containing this dimension
in an unmodified state (no hidden or disabled levels or calculated members
added) then you should be able to browse.

- Matt Carroll
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Eugene" <shieug123@yahoo.com> wrote in message
news:da0b8ea2.0307230759.7b253426@posting.google.c om...
> Hi, Matt,
>
>
> The message is still"Unable to brouse to dimension'New Dimesion'. The
> dimension cannot be displayed until a cube that contains it has been
> processed", even after I checked the "ordering & uniqueness of
> members" option in the select advanced option window.
>
> Kevin,
>
> Say, I have a employee dimension for some fact table. Link to the
> employee dimension, say I has a secondary dimension called:
> officebuilding, which I have to model it as many-to-many to the
> employee dimension, so I have to have a link table called: emp_office
> table. I don't know how can I build a view to avoid them.
>
> Thanks so much for all the inputs.
>
>
> Eugene
>
> "Kevin" <ReplyTo@Newsgroups.only> wrote in message
news:<#koLisIUDHA.940@TK2MSFTNGP11.phx.gbl>...
> > You might also try creating what look like pure star schema views on top
of
> > your snowflakes.
> >
> > ----------------------------------------------------
> > The views expressed here are my own
> > and not of my employer.
> > ----------------------------------------------------
> > "Matt Carroll [MS]" <MattCar@online.microsoft.com> wrote in message
> > news:OXc7sXHUDHA.2316@tk2msftngp13.phx.gbl...
> > > Check the settings of Member Keys Unique and Member Names Unique
> > properties
> > > in the advanced tab on the level. If this doesn't work, what error
are
> > you
> > > seeing during processing?
> > >
> > > - Matt Carroll
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > > "Eugene" <shieug123@yahoo.com> wrote in message
> > > news:da0b8ea2.0307220810.554520ea@posting.google.c om...
> > > > Hi,
> > > >
> > > >
> > > > I run into the problem when I learn and practice the dimensional
> > > > modeling. I try to use snowflake schema and my secondary dimentional
> > > > tables (those dimentional tables link to the first level dimensional
> > > > tables but not directly link to the fact table) have many-to-many
> > > > relasionship with the first level dimentional tables, so I have to
use
> > > > a link table between those relasionship, but when I do so, the
> > > > processing failed in SQL Server OLAP environment.
> > > >
> > > > Am I doing something wrong here? Or what should be the correct way
to
> > > > do that?
> > > >
> > > > Thanks in advance for all the help!
> > > >
> > > >
> > > > Eugene
> > >
> > >

Matt,


Thanks for the hint. I do see the data which was
processed even though it said: unable to prcess. It
proves to me that it can handle many-to-many
relationship in the dimensional parts. I do appreciate
it.


Eugene


"Matt Carroll [MS]" <MattCar@online.microsoft.com> wrote in message news:<eCr0mmTUDHA.2280@TK2MSFTNGP10.phx.gbl>...
> This message means that the AS UI is not able to simulate the data contained
> in the dimension using a local cube. This may be because the estimated size
> of the dimension is large or possibly because it uses a feature not
> supported in local cubes. If you process a cube containing this dimension
> in an unmodified state (no hidden or disabled levels or calculated members
> added) then you should be able to browse.
>
> - Matt Carroll
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Eugene" <shieug123@yahoo.com> wrote in message
> news:da0b8ea2.0307230759.7b253426@posting.google.c om...
> > Hi, Matt,
> >
> >
> > The message is still"Unable to brouse to dimension'New Dimesion'. The
> > dimension cannot be displayed until a cube that contains it has been
> > processed", even after I checked the "ordering & uniqueness of
> > members" option in the select advanced option window.
> >
> > Kevin,
> >
> > Say, I have a employee dimension for some fact table. Link to the
> > employee dimension, say I has a secondary dimension called:
> > officebuilding, which I have to model it as many-to-many to the
> > employee dimension, so I have to have a link table called: emp_office
> > table. I don't know how can I build a view to avoid them.
> >
> > Thanks so much for all the inputs.
> >
> >
> > Eugene
> >
> > "Kevin" <ReplyTo@Newsgroups.only> wrote in message
> news:<#koLisIUDHA.940@TK2MSFTNGP11.phx.gbl>...
> > > You might also try creating what look like pure star schema views on top
> of
> > > your snowflakes.
> > >
> > > ----------------------------------------------------
> > > The views expressed here are my own
> > > and not of my employer.
> > > ----------------------------------------------------
> > > "Matt Carroll [MS]" <MattCar@online.microsoft.com> wrote in message
> > > news:OXc7sXHUDHA.2316@tk2msftngp13.phx.gbl...
> > > > Check the settings of Member Keys Unique and Member Names Unique
> properties
> > > > in the advanced tab on the level. If this doesn't work, what error
> are
> you
> > > > seeing during processing?
> > > >
> > > > - Matt Carroll
> > > > --
> > > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > > >
> > > > "Eugene" <shieug123@yahoo.com> wrote in message
> > > > news:da0b8ea2.0307220810.554520ea@posting.google.c om...
> > > > > Hi,
> > > > >
> > > > >
> > > > > I run into the problem when I learn and practice the dimensional
> > > > > modeling. I try to use snowflake schema and my secondary dimentional
> > > > > tables (those dimentional tables link to the first level dimensional
> > > > > tables but not directly link to the fact table) have many-to-many
> > > > > relasionship with the first level dimentional tables, so I have to
> use
> > > > > a link table between those relasionship, but when I do so, the
> > > > > processing failed in SQL Server OLAP environment.
> > > > >
> > > > > Am I doing something wrong here? Or what should be the correct way
> to
> > > > > do that?
> > > > >
> > > > > Thanks in advance for all the help!
> > > > >
> > > > >
> > > > > Eugene
> > > >
> > > >