dbTalk Databases Forums  

Member Name Column property

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss Member Name Column property in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Jesse O
 
Posts: n/a

Default Member Name Column property - 11-14-2005 , 01:50 PM






Quite often the name of something will change in the source system, say
someone gets married. Their ID stays the same, just the name changes. No new
surrogate key, no new busienss key. The Member Key is the same.

In AS, I'd like this change in names to be reflected. Does the dimension
have to be set to changing in order to do so?



Reply With Quote
  #2  
Old   
Darren Gosbell
 
Posts: n/a

Default Re: Member Name Column property - 11-14-2005 , 04:53 PM






No, as long as you have the ID column setup as the member key, you can
change the member name by simply incrementally processing the dimension
(assuming it is a shared dimension)

The changing property relates to the structure of the dimension. One
example would be if you had an employee dimension and you wanted to move
an employee to a different manager and you wanted to be able to do this
without fully re-processing the cube, then you would need to set the
dimension as changing.

Note: Parent-Child dimensions are inherently changing, due to the way
their structure is defined.

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <egqAaSV6FHA.2012 (AT) TK2MSFTNGP14 (DOT) phx.gbl>, jesperzz (AT) hotmail (DOT) com
says...
Quote:
Quite often the name of something will change in the source system, say
someone gets married. Their ID stays the same, just the name changes. No new
surrogate key, no new busienss key. The Member Key is the same.

In AS, I'd like this change in names to be reflected. Does the dimension
have to be set to changing in order to do so?





Reply With Quote
  #3  
Old   
Jesse O
 
Posts: n/a

Default Re: Member Name Column property - 11-14-2005 , 05:30 PM



That's what I thought as well...however the name updates aren't happening,
they're only occuring in the changing dimensions.

Weird.

"Darren Gosbell" <jam (AT) newsgroups (DOT) nospam> wrote

Quote:
No, as long as you have the ID column setup as the member key, you can
change the member name by simply incrementally processing the dimension
(assuming it is a shared dimension)

The changing property relates to the structure of the dimension. One
example would be if you had an employee dimension and you wanted to move
an employee to a different manager and you wanted to be able to do this
without fully re-processing the cube, then you would need to set the
dimension as changing.

Note: Parent-Child dimensions are inherently changing, due to the way
their structure is defined.

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <egqAaSV6FHA.2012 (AT) TK2MSFTNGP14 (DOT) phx.gbl>, jesperzz (AT) hotmail (DOT) com
says...
Quite often the name of something will change in the source system, say
someone gets married. Their ID stays the same, just the name changes. No
new
surrogate key, no new busienss key. The Member Key is the same.

In AS, I'd like this change in names to be reflected. Does the dimension
have to be set to changing in order to do so?







Reply With Quote
  #4  
Old   
Darren Gosbell
 
Posts: n/a

Default Re: Member Name Column property - 11-15-2005 , 01:05 AM



That is a bit strange, I have not had to do this in a production
environment, so I actually checked in BOL before posting. Under
incremental processing of shared dimensions and it said the following:

<snip>
Because almost any property of a member can be changed by changing the
appropriate field in the underlying dimension table, it is possible to
have changed member names after the dimension is incrementally updated.
</snip>

Are you on the latest SP? If so, and you can reproduce the issue it may
be an idea to report to MS. If you have sensitive data or large cubes,
see if you can reproduce the situation in the Foodmart database.

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <O4eyfNX6FHA.1864 (AT) TK2MSFTNGP12 (DOT) phx.gbl>, jesperzz (AT) hotmail (DOT) com
says...
Quote:
That's what I thought as well...however the name updates aren't happening,
they're only occuring in the changing dimensions.

Weird.

"Darren Gosbell" <jam (AT) newsgroups (DOT) nospam> wrote in message
news:MPG.1de3c04a2463c74f9897ba (AT) news (DOT) microsoft.com...
No, as long as you have the ID column setup as the member key, you can
change the member name by simply incrementally processing the dimension
(assuming it is a shared dimension)

The changing property relates to the structure of the dimension. One
example would be if you had an employee dimension and you wanted to move
an employee to a different manager and you wanted to be able to do this
without fully re-processing the cube, then you would need to set the
dimension as changing.

Note: Parent-Child dimensions are inherently changing, due to the way
their structure is defined.

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <egqAaSV6FHA.2012 (AT) TK2MSFTNGP14 (DOT) phx.gbl>, jesperzz (AT) hotmail (DOT) com
says...
Quite often the name of something will change in the source system, say
someone gets married. Their ID stays the same, just the name changes. No
new
surrogate key, no new busienss key. The Member Key is the same.

In AS, I'd like this change in names to be reflected. Does the dimension
have to be set to changing in order to do so?









Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.