dbTalk Databases Forums  

64000 Member problem

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


Discuss 64000 Member problem in the microsoft.public.sqlserver.olap forum.



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

Default 64000 Member problem - 08-28-2003 , 08:06 PM






Hi all
I have a problem that has got me completely stumped

I have a cube that has 1 dimension in it for Mail Address info
Level FromDomain
Level FromUser

we had a problem a while ago where the FromDomain Member Count exceeded
64000
so we implemented Automatic Grouping for the FromDomain Level and set
Visible to False
So I have the following levels:
DomainGrouping (auto grouping)
FromDomain (unique keys, unique names)
FromUser (unique keys)

This has worked fine until now where the FromUser Level now has more that
64000 members for a single Domain

I have attempted to add another Auto Grouping Level for the FromUser, but
have been unsuccessful as every time I set the level to Automatic Grouping
the editor automatically changes the unique keys and unique names values to
False. But All levels after an auto grouping level must have unique keys.

I've attempted to implement it with my own grouping in the following way:
DomainGrouping with key as Left(FromDomain, 1) as a hidden level
FromDomain
UserGrouping with key as FromDomain + ' - ' + Left(FromUser, 1) as a hidden
level
FromUser with key as complete email address and name as just the first part
of the address (user)

but now the FromUser name must be unique as it is the first visible level
after a hidden level must also have unique names (not just unique keys)

This structure only works if my UserGrouping Level is visible


Can anyone please help me?

Regards
Aaron



Reply With Quote
  #2  
Old   
Aaron Lister
 
Posts: n/a

Default Re: 64000 Member problem - 08-28-2003 , 08:43 PM






I tried that, but it doesn't let me.

I get an error along the lines of:

All levels after a hidden level must have unique keys, and the first visible
level after a hidden level must have unique names

Aaron

"Mosha Pasumansky [MS]" <moshap (AT) microsoft (DOT) com> wrote

Quote:
but now the FromUser name must be unique as it is the first visible
level
after a hidden level must also have unique names (not just unique keys)

Can you try to set "Allow Duplicate Names" property to true, and see if
this
helps ?

HTH,
Mosha

--
==================================================
Mosha Pasumansky - www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================





Reply With Quote
  #3  
Old   
Mosha Pasumansky [MS]
 
Posts: n/a

Default Re: 64000 Member problem - 08-28-2003 , 08:52 PM



Quote:
I tried that, but it doesn't let me.

I get an error along the lines of:

All levels after a hidden level must have unique keys, and the first
visible
level after a hidden level must have unique names
This could be a wrong error message. What if you do this change in DSO
directly ?

--
==================================================
Mosha Pasumansky - www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================




Reply With Quote
  #4  
Old   
Mosha Pasumansky [MS]
 
Posts: n/a

Default Re: 64000 Member problem - 08-29-2003 , 12:50 PM



I know. But the reason why this error message shows up is because when you
hide a level, members which were not used to be siblings may become
siblings.

--
==================================================
Mosha Pasumansky - www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================
"Aaron Lister" <alister (AT) ems-global (DOT) com> wrote

Quote:
Mosha

The "Allow Duplicate Names" property is to allow duplicate names for
children of the same member. But where my duplicates appear is on
different
members

For example:
FromDomain: Yahoo.com FromUser: billy
FromDomain: microsoft.com FromUser: billy

Aaron


"Mosha Pasumansky [MS]" <moshap (AT) microsoft (DOT) com> wrote in message
news:3f4eb200$1 (AT) news (DOT) microsoft.com...
I tried that, but it doesn't let me.

I get an error along the lines of:

All levels after a hidden level must have unique keys, and the first
visible
level after a hidden level must have unique names

This could be a wrong error message. What if you do this change in DSO
directly ?

--
==================================================
Mosha Pasumansky - www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================







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.