dbTalk Databases Forums  

changes between 2000 and 2005

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


Discuss changes between 2000 and 2005 in the microsoft.public.sqlserver.olap forum.



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

Default changes between 2000 and 2005 - 01-17-2006 , 10:36 AM






When doing a Discover "MDSCHEMA_MEMBERS"

2000:
<row><Member_Unique_Name>[Store].[All
Stores].[Canada].[BC]</Member_Unique_Name></row>

2005:
<row><Member_Unique_Name>[Store].[Store
State].&amp;[BC]</Member_Unique_Name></row>

Is there a setting which will make it behave like in AS 2000?

Chris



Reply With Quote
  #2  
Old   
Akshai Mirchandani [MS]
 
Posts: n/a

Default Re: changes between 2000 and 2005 - 01-17-2006 , 10:50 AM






Cross posting reply.

Sorry, but I have to ask the age-old unique name question -- why should it
matter?

There is actually a setting on the cube -- in the Cube Structure tab, select
the dimension and change the MemberUniqueNameStyle to NamePath. I believe
this should change the unique name style to follow the 2000 construction.

Thanks,
Akshai
--
This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"ChrisHarrington" <charrington-at-activeinterface.com> wrote

Quote:
When doing a Discover "MDSCHEMA_MEMBERS"

2000:
row><Member_Unique_Name>[Store].[All
Stores].[Canada].[BC]</Member_Unique_Name></row

2005:
row><Member_Unique_Name>[Store].[Store
State].&amp;[BC]</Member_Unique_Name></row

Is there a setting which will make it behave like in AS 2000?

Chris




Reply With Quote
  #3  
Old   
Chris Webb
 
Posts: n/a

Default RE: changes between 2000 and 2005 - 01-17-2006 , 11:03 AM



Does setting the connection string property MDX Unique Name Style=2 do the
trick? Or setting the MemberUniqueNameStyle property to NamePath on each cube
dimension?
--
Blog at:
http://spaces.msn.com/members/cwebbbi/


"ChrisHarrington" wrote:

Quote:
When doing a Discover "MDSCHEMA_MEMBERS"

2000:
row><Member_Unique_Name>[Store].[All
Stores].[Canada].[BC]</Member_Unique_Name></row

2005:
row><Member_Unique_Name>[Store].[Store
State].&[BC]</Member_Unique_Name></row

Is there a setting which will make it behave like in AS 2000?

Chris




Reply With Quote
  #4  
Old   
ChrisHarrington
 
Posts: n/a

Default Re: changes between 2000 and 2005 - 01-17-2006 , 12:17 PM



More on this issue...

When running MDX queries the NamePath behavior is what it was with AS 2000.
But the Discover MDSCHEMA_MEBERS doesn't seem now to pay attention to that
setting.

Chris Harrington

"Chris Webb" <OnlyForPostingToNewsgroups (AT) hotmail (DOT) com> wrote

Quote:
Does setting the connection string property MDX Unique Name Style=2 do the
trick? Or setting the MemberUniqueNameStyle property to NamePath on each
cube
dimension?
--
Blog at:
http://spaces.msn.com/members/cwebbbi/


"ChrisHarrington" wrote:

When doing a Discover "MDSCHEMA_MEMBERS"

2000:
row><Member_Unique_Name>[Store].[All
Stores].[Canada].[BC]</Member_Unique_Name></row

2005:
row><Member_Unique_Name>[Store].[Store
State].&[BC]</Member_Unique_Name></row

Is there a setting which will make it behave like in AS 2000?

Chris






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.