dbTalk Databases Forums  

hitting the 64k limit with a hierarchial big dimension - Please ad

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


Discuss hitting the 64k limit with a hierarchial big dimension - Please ad in the microsoft.public.sqlserver.olap forum.



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

Default hitting the 64k limit with a hierarchial big dimension - Please ad - 05-04-2005 , 11:48 AM






Hi,

I have a big dimension with 4 levels including the "All" level. The second
level (The level below the "All" Level) has more than 64k members and MSAS
could not process the dimension.

I could not do "Auto - Grouping" as this is not the lowest level. Please
advice if there is a work around for this without changing the table
structure like adding new columns.

Thanks,

Sam.

Reply With Quote
  #2  
Old   
David Botzenhart
 
Posts: n/a

Default Re: hitting the 64k limit with a hierarchial big dimension - Please ad - 05-04-2005 , 10:13 PM






Unfortunatly, the only thing you could do is add your own grouping to break
up the first level.

David

"Prasad" <Prasad (AT) discussions (DOT) microsoft.com> wrote

Quote:
Hi,

I have a big dimension with 4 levels including the "All" level. The second
level (The level below the "All" Level) has more than 64k members and MSAS
could not process the dimension.

I could not do "Auto - Grouping" as this is not the lowest level. Please
advice if there is a work around for this without changing the table
structure like adding new columns.

Thanks,

Sam.



Reply With Quote
  #3  
Old   
Dave Wickert [MSFT]
 
Posts: n/a

Default Re: hitting the 64k limit with a hierarchial big dimension - Please ad - 05-04-2005 , 11:18 PM



A common technique is:
1) load the dimension through a view; not the base table (always a best
practice)
2) in the view add a column which is the first 2 characters of the 2nd
level's name.
3) use this column to create a level between All and your 2nd level.
Basically you are forcing an intermediatary grouping level.

Hope that helps.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"David Botzenhart" <David.Botzenhart (AT) mariner (DOT) usa.com> wrote

Quote:
Unfortunatly, the only thing you could do is add your own grouping to
break
up the first level.

David

"Prasad" <Prasad (AT) discussions (DOT) microsoft.com> wrote in message
news:583CB489-99B2-406F-B1F9-FF97DA1004F4 (AT) microsoft (DOT) com...
Hi,

I have a big dimension with 4 levels including the "All" level. The
second
level (The level below the "All" Level) has more than 64k members and
MSAS
could not process the dimension.

I could not do "Auto - Grouping" as this is not the lowest level. Please
advice if there is a work around for this without changing the table
structure like adding new columns.

Thanks,

Sam.





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.