I created a SQL table with 2 rows as shown:

ID LastName FirstName
1 Jones Bob
2 Jones Tom

I then created a cube with Dimension LastName. I create a FirstName member
-property for the LastName of the LastName dimension.

I queried to show the LastName on rows and the FirstName member prop on
columns. The FirstName displayed was Tom. In this scenario, is the value of
the member prop returned deterministic?

If I added a 3rd row to SQL: 3 Jones Ken
and execute an incremental process to pull in the new row, can I count on
the FirstName for Jones returning the new value?

Thanks,

LMcPhee

For both AS 2000 and AS 2005, there should be a single value of a Member
Property (aka Attribute Relationship in AS 2005) for a given member. So,
while it's interesting to experiment with what gets returned when a
Member Property could take multiple values, it might not be something
you wish to hang your hat on:

http://msdn.microsoft.com/library/de.../en-us/olapdma
d/agenhancingdims_3okz.asp
Before you create a member property in a dimension level with a source
column containing nonunique values, you must ensure that each member in
the level can have only one value for each member property. Otherwise,
member property values will be incomplete and misleading because only
one value can be displayed for each member. For example, values in the
source column of the Salesperson level are not unique. Each Salesperson
can have only one Manager, so Manager is a valid member property in the
Salesperson level. However, a Salesperson can work in multiple Regions,
so Region is not a valid member property. If Region were defined as a
member property, it would display only one Region to end users, even for
Salespersons who work in multiple Regions.
...
http://msdn2.microsoft.com/en-us/lib...S,SQL.90).aspx
The main constraint when you create an attribute relationship is to make
sure that the attribute referred to by the attribute relationship has no
more than one value for any member in the attribute to which the
attribute relationship belongs. For example, if you define a
relationship between a City attribute and a State attribute, each city
can only relate to a single state.
...

- Deepak

Deepak Puri
Microsoft MVP - SQL Server

*** Sent via Developersdex http://www.developersdex.com ***

In my case I have a Location dimension which has a Description member-prop.
It would be very rare, but on occasion a Location's Description could change.
I have event data on which I am displaying "Top N" most frequent Locations
for events. Customer wants to see a Description column. I would like the
Description to show latest Description for the Location. But I don't want to
do a full porcess of the cube to get it.

If I keep track of changes to Description for each Location, can I
programatically change the Description member prop of a specific member?

LMcPhee

"Deepak Puri" wrote:

Assuming that you're using AS 2000 and Locations is a shared dimension,
you can change the Description Member Property with an incremental
update of the dimension - no reprocessing of the cube needed.


- Deepak

Deepak Puri
Microsoft MVP - SQL Server

*** Sent via Developersdex http://www.developersdex.com ***

I am using AS 2000. I thought of making Location a shared dim, but that did
not work. The dimension table does NOT have any new members - just changing
the Description when the Location value is already a member of the Dimension.

e.g.
FactTable LocDimTable
ID LocationID LocationID Location Description
========== ======================
1 1 1 Loc1 Loc1
description
2 1

I create a shared dim for Location, with Description for its member-prop and
process the cube.
If I just change the Description for Loc1 and do incremental process of
Location dim, no change to member-prop in cube.
If I add a new row to FactTable with LocationID =1, and change Description,
then Incremental process of cube, checking off Incremental process of dims,
still Description shows original value. Am I missing something here?

LMcPhee


"Deepak Puri" wrote:

Here's what worked with Foodmart 2000:

- Create Excel 2003 pivot table for Warehouse cube, showing Stores on
rows, with "Store Manager" Property.

- Update "Store Manager" for Store 2 (Bellingham) from Smith to Brown in
the Foodmart 2000 data source.

- Refresh pivot data - Store 2 Manager is still Smith

- Incrementally update Foodmart Store dimension

- Refresh pivot data - Store 2 Manager now shows Brown


- Deepak

Deepak Puri
Microsoft MVP - SQL Server

*** Sent via Developersdex http://www.developersdex.com ***