AMO- Data Source View not updated

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: DBOwner <nadavNeu.GGroups@xxxxxxxxx>
Date: Tue, 24 Jul 2007 02:01:40 -0700

Hi guys,
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
hierarchy level can be added if needed.

when i get to the my AMO application i check if the structure of the
dimension should be changed.
the problem is that for some strange reason although i update both the
DataSource and the DSV, the table structure held in the DSV is not
updated to the new Table Structure.
i tried both update types (UpdateOptions.ExpandFull ,
alterDependants)

also refresh does no good.
Does anyone have an idea how to update the Daatasource view to match
the current state of the DB ??

Thanjs

.

Follow-Ups:
- Re: AMO- Data Source View not updated
  - From: Nadav

Prev by Date: Re: Getting Levels 1 + 2 of Hierarchy in column output
Next by Date: Re: Slow performance in Excel
Previous by thread: How to fetch a column in OLAP Cube and use it in VB.net application
Next by thread: Re: AMO- Data Source View not updated
Index(es):
- Date
- Thread

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)
Re: Bug in CurrentMember.Name
... would put their hierarchies in separate dimensions. ... their own calculations and those calculations are probably going to want the ... Resellers' for every row while the calculated measure Reseller Order ...
(microsoft.public.sqlserver.olap)
Re: PC dimension with aggregations
... I use this technique when I deal with small (up to 10 levels deep) PC hierarchies. ... The PC dimensions are defined by default as "changeable" so no aggregations will be saved on it. ... It will be nice to have an option to mark the PC dimension as non-changeable and then to have the possibility to design aggregations for it. ...
(microsoft.public.sqlserver.olap)
Re: Bug in CurrentMember.Name
... But it is simple enough to introduce the isolation between hierarchies ... by splitting them into separate dimensions just like AS 2000 did. ... In the sample query I've explicitely specified that the current member of ... Resellers' for every row while the calculated measure Reseller Order ...
(microsoft.public.sqlserver.olap)
Re: MSAS Database Migrations of 2000 to 2005 - Hierarchical Dimensions
... What has happened is that the migration wizard was unable to migrate the ... multiple hierarchies was really just a naming convention. ... I would keep the other "ProjectN" dimensions around in a database ...
(microsoft.public.sqlserver.olap)