Hi,

I have a problem with a large dimension where automatic grouping is used.
Its the same problem mentioned in the MSDN article: 'OLAP Services: Working
with Large Levels', but in a different scenario.

The problem is this: My client app generates the DrillThrough MDX query
based on the cell that the user clicked. Then this query is moved to a
stored proc where Openqeury function is used (with linked servers) to
execute the DrillThrough query and get the results. Now when my client app
itself does the drillthru it works fine since the metadata has reached the
client by the time the drillthrough is done.

The problem is when the drillthrough query is executed in the stored proc.
It gives the error - 'Cannot find dimension member...in a name binding
funtion'.
Does anyone have a solution for resolving this? I know that using the fully
qualified member name in the DrillThrough query would do the trick, but the
problem is that my client app doesn't generate queries with fully qualified
member names. Is there any other way that this can be handled?

To illustrate, here are two different queries which are similar, but one
works while the other doesn't:

NON-Working query:
Select * from Openquery(OLAP,
'DRILLTHROUGH SELECT FROM [Procedure] WHERE ( [Patient Id].[Patient
Id].&[28707] )')

Working query:
Select * from Openquery(OLAP,
'DRILLTHROUGH SELECT FROM [Procedure] WHERE ( [Patient Id].[All Patient
Id].[000000010 - 005981721].[002424649] )')


FYI: The member [000000010 - 005981721] that you see in the working query is
the level at which automatic grouping was enabled (due to large # of
dimension members).

All suggestions are appreciated.
Thanks,
Chumma Dede

What is the unique name for that member ?

--
==================================================
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.
==================================================
"Chumma Dede" <deja.removethis (AT) chothu (DOT) mailshell.com> wrote

Sorry for the delay in responding.

Mosha, I'm not sure what you mean. The "Member Names Unique" property is set
to False. The name for that member is [002424649] (this is what appears on
the Front End). Is this what you meant?

I also noticed that setting the VLDMThreshold value in the registry solves
the problem. The error only seems to occur if the VLD Manager gets invoked
to handle the dimension. Are there any workarounds for this other than
having to increase the Threshold? What would be the consequences of
increasing the Threshold such that the VLD Manager doesn't get invoked?

I'm a relative newbie at OLAP so I appreciate your patience.

Thanks.
Chumma

Mosha, Are there any specific newsgroups for Yukon?
Thanks

"Chumma Dede" <deja.removethis (AT) chothu (DOT) mailshell.com> wrote

Yes, but those are private newsgroups available only to the participants in
the Yukon Beta program.
Contact me offline if you are interested to join Yukon Beta program.

--
==================================================
Mosha Pasumansky - http://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.
==================================================