 | |
64,000 limit reached
microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
64,000 limit reached -
12-22-2004
, 12:59 PM
#2
| |||
| |||
|
|
I have the following: 329162 Accounts 329242 Cards I can have 0-many cards to 1 account I currently do not have more than 3 cards to 1 account My dimension: Accounts ----Cards So my parent is Accounts and my children is cards. I know MS OLAP limitation is 64,000 children members but I only have 3 children members at max to one parent. I'm getting the maximum 64k limit has been reached. What am I doing wrong or what am I not understanding. |
#3
| |||
| |||
|
|
If the (All) level is enabled then the [All Acounts] member would have 329162 children. You can disable this label or group accounts so as to avoid the 64k limit. HTH, Brian www.geocities.com/brianaltmann/olap.html "Tim" wrote: I have the following: 329162 Accounts 329242 Cards I can have 0-many cards to 1 account I currently do not have more than 3 cards to 1 account My dimension: Accounts ----Cards So my parent is Accounts and my children is cards. I know MS OLAP limitation is 64,000 children members but I only have 3 children members at max to one parent. I'm getting the maximum 64k limit has been reached. What am I doing wrong or what am I not understanding. |
#4
| |||
| |||
|
|
Thanks for the reply. In dimension editor I have changed the advanced properties of 'All Level' to No. When I rebuild the dimension I still get the 64k error. Am I missing something else. |
members at the first level are still considered children of some hypotetical
parent - therefore there could not be more then 64000 (not 64K !) members at
the first level.
--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebLog/mosha
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.
==================================================
#5
| |||
| |||
|
|
Thanks for the reply. In dimension editor I have changed the advanced properties of 'All Level' to No. When I rebuild the dimension I still get the 64k error. Am I missing something else. It is actually not important whether or not there is All level, since members at the first level are still considered children of some hypotetical parent - therefore there could not be more then 64000 (not 64K !) members at the first level. -- ================================================== Mosha Pasumansky - http://www.mosha.com/msolap Analysis Services blog at http://www.sqljunkies.com/WebLog/mosha 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. ================================================== |
#6
| |||
| |||
|
|
Mosha, Thanks for the clearification. Since you know my scenario, what is the best way to solve my issue? Other words, what can I do to get the above to work. "Mosha Pasumansky [MS]" <moshap (AT) online (DOT) microsoft.com> wrote in message news:OBELs2J6EHA.540 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Thanks for the reply. In dimension editor I have changed the advanced properties of 'All Level' to No. When I rebuild the dimension I still get the 64k error. Am I missing something else. It is actually not important whether or not there is All level, since members at the first level are still considered children of some hypotetical parent - therefore there could not be more then 64000 (not 64K !) members at the first level. -- ================================================== Mosha Pasumansky - http://www.mosha.com/msolap Analysis Services blog at http://www.sqljunkies.com/WebLog/mosha 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. ================================================== |
#7
| |||
| |||
|
|
Try to create a parent level of the level "Account" in your dimension. You can use an ad hoc column in the dimension table or use "Automatic grouping" property in Analysis Manager. Francesco Anti "Tim" <Tim (AT) NOSpam (DOT) com> ha scritto nel messaggio news:u9ecnwM6EHA.3828 (AT) TK2MSFTNGP09 (DOT) phx.gbl... Mosha, Thanks for the clearification. Since you know my scenario, what is the best way to solve my issue? Other words, what can I do to get the above to work. "Mosha Pasumansky [MS]" <moshap (AT) online (DOT) microsoft.com> wrote in message news:OBELs2J6EHA.540 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Thanks for the reply. In dimension editor I have changed the advanced properties of 'All Level' to No. When I rebuild the dimension I still get the 64k error. Am I missing something else. It is actually not important whether or not there is All level, since members at the first level are still considered children of some hypotetical parent - therefore there could not be more then 64000 (not 64K !) members at the first level. -- ================================================== Mosha Pasumansky - http://www.mosha.com/msolap Analysis Services blog at http://www.sqljunkies.com/WebLog/mosha 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. ================================================== |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.