Re: MSAS 2002 to MSAS 2005 Migration: DSV Question.



in 1 DSV you can create "views" (not SQL views)
in these "views" you can display only the table you want.
the "default view" contains all the tables.

lookat the upper left of the DSV screen to create a new one.

"Prasad" <Prasad@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:128A49B5-D388-43B5-AE34-4DE319BF0CF0@xxxxxxxxxxxxxxxx
> Hi,
>
> In our old MSAS 2000 we have about 20 physical cubes (20 fact tables and
> around 300 rollup tables). Everything is created in 1 data base. Some of
> the
> physicsl cubes share dimensions (rollup tables).
>
> When we migrated to MSAS 2005 with the help of Migration wizard, it
> created
> 1 huge DSV with 20 fact tables and 300 rollup tables. As you can
> understand
> the DSV is unmanageable and very hard to interpret.
>
> Please suggest any alternative designs.
>
> One thing i did is to break the one huge DSV into multiple logical smaller
> DSV's to easily manage. the problem is once i start building physical
> cubes
> from these different DSV's, each cube created its own copy of the
> dimension
> as the source DSV is different.
>
> Now that i have 5 logical DSV's and some common shared dimensions, i have
> multiple copies of the same dimensions with different names. More over the
> dimension names it created are meaningless.
>
> Please comment.
>
> Thanks,
>
> Sam.


.



Relevant Pages

  • Re: AMO- Data Source View not updated
    ... I'm working on a project where i dynamicly build the hierarchies of ... some of my dimensions. ... the source table in the SQL server are updated dynamiclly each time a ... DataSource and the DSV, the table structure held in the DSV is not ...
    (microsoft.public.sqlserver.olap)
  • AMO- Data Source View not updated
    ... I'm working on a project where i dynamicly build the hierarchies of ... some of my dimensions. ... the source table in the SQL server are updated dynamiclly each time a ... DataSource and the DSV, the table structure held in the DSV is not ...
    (microsoft.public.sqlserver.olap)
  • Re: Binding Too Small
    ... The column binding on one of the dimensions was still set to the former ... The DSV was updated to nvarchar, ... expand the Source property until you find the data type and size. ...
    (microsoft.public.sqlserver.olap)
  • Re: SSAS 2005-can browse but cannot see measures in processed cube
    ... 2, and have set up a couple of dsv, and a couple of cubes. ... yesterday all cubes that go against a particular Data Source (dsv) ... dimensions set so it did not have an "All" level, ...
    (microsoft.public.sqlserver.olap)
  • Re: SSAS 2005-can browse but cannot see measures in processed cube
    ... I've been trucking along quite well using SSAS 2005 with Service Pack ... 2, and have set up a couple of dsv, and a couple of cubes. ... yesterday all cubes that go against a particular Data Source (dsv) ...
    (microsoft.public.sqlserver.olap)