dbTalk Databases Forums  

MDX Compatibility Property

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


Discuss MDX Compatibility Property in the microsoft.public.sqlserver.olap forum.



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

Default MDX Compatibility Property - 07-04-2006 , 08:43 PM






Hi

We have a ragged dimension where we hide the members if they have an empty
name. I found some documentation here (
http://msdn2.microsoft.com/en-us/library/ms365406.aspx ) on how to handle
them. We have a custom web browser to view the members in the the
dimensions/hierarchies and use MDX to retrieve the members. When we set the
MDX Compatibility property to 2, the members are presented correctly with
the blank members ommitted from the list.

This all works fine but now the following MDX now fails with Exception
"Internal error: An unexpected exception occured."

SELECT [dimension].[hierarchy].members ON 0, {} ON 1 FROM [cubeName]

or

SELECT [dimension].[hierarchy].AllMembers ON 0, {} ON 1 FROM [cubeName]

If Compatibility is not set to 2 in the connection string the above
statements work.

Any ideas why this now doesn't work or an alternative way to retrieve all
the members from a hierarchy? We are using SSAS 2005 with ADOMD.net v9.

Full stack trace follows

" at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.XmlaClientProvider.Microsoft.AnalysisServices .AdomdClient.IExecuteProvider.ExecuteMultidimensio nal(ICommandContentProvider
contentProvider, AdomdPropertyCollection commandProperties,
IDataParameterCollection parameters)\r\n at
Microsoft.AnalysisServices.AdomdClient.AdomdComman d.ExecuteCellSet() "


tia



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

Default Re: MDX Compatibility Property - 07-05-2006 , 04:51 PM






Are you on SP1 of AS? I recall a bug was fixed for this in SP1...

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

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.

"Graham Lloyd" <gilly1409 (AT) hotmail (DOT) com> wrote

Quote:
Hi

We have a ragged dimension where we hide the members if they have an empty
name. I found some documentation here (
http://msdn2.microsoft.com/en-us/library/ms365406.aspx ) on how to handle
them. We have a custom web browser to view the members in the the
dimensions/hierarchies and use MDX to retrieve the members. When we set
the MDX Compatibility property to 2, the members are presented correctly
with the blank members ommitted from the list.

This all works fine but now the following MDX now fails with Exception
"Internal error: An unexpected exception occured."

SELECT [dimension].[hierarchy].members ON 0, {} ON 1 FROM [cubeName]

or

SELECT [dimension].[hierarchy].AllMembers ON 0, {} ON 1 FROM [cubeName]

If Compatibility is not set to 2 in the connection string the above
statements work.

Any ideas why this now doesn't work or an alternative way to retrieve all
the members from a hierarchy? We are using SSAS 2005 with ADOMD.net v9.

Full stack trace follows

" at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.XmlaClientProvider.Microsoft.AnalysisServices .AdomdClient.IExecuteProvider.ExecuteMultidimensio nal(ICommandContentProvider
contentProvider, AdomdPropertyCollection commandProperties,
IDataParameterCollection parameters)\r\n at
Microsoft.AnalysisServices.AdomdClient.AdomdComman d.ExecuteCellSet() "


tia




Reply With Quote
  #3  
Old   
G_NoSpam
 
Posts: n/a

Default Re: MDX Compatibility Property - 07-05-2006 , 05:22 PM



Hi Akshai - thatnks for the response

We are using SP1. Any other ideas? All the other dimesnions that don't have
hidden members work ok!






"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote

Quote:
Are you on SP1 of AS? I recall a bug was fixed for this in SP1...

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

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.

"Graham Lloyd" <gilly1409 (AT) hotmail (DOT) com> wrote in message
news:%23ZLFlR9nGHA.4340 (AT) TK2MSFTNGP05 (DOT) phx.gbl...
Hi

We have a ragged dimension where we hide the members if they have an
empty name. I found some documentation here (
http://msdn2.microsoft.com/en-us/library/ms365406.aspx ) on how to handle
them. We have a custom web browser to view the members in the the
dimensions/hierarchies and use MDX to retrieve the members. When we set
the MDX Compatibility property to 2, the members are presented correctly
with the blank members ommitted from the list.

This all works fine but now the following MDX now fails with Exception
"Internal error: An unexpected exception occured."

SELECT [dimension].[hierarchy].members ON 0, {} ON 1 FROM [cubeName]

or

SELECT [dimension].[hierarchy].AllMembers ON 0, {} ON 1 FROM [cubeName]

If Compatibility is not set to 2 in the connection string the above
statements work.

Any ideas why this now doesn't work or an alternative way to retrieve all
the members from a hierarchy? We are using SSAS 2005 with ADOMD.net v9.

Full stack trace follows

" at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.XmlaClientProvider.Microsoft.AnalysisServices .AdomdClient.IExecuteProvider.ExecuteMultidimensio nal(ICommandContentProvider
contentProvider, AdomdPropertyCollection commandProperties,
IDataParameterCollection parameters)\r\n at
Microsoft.AnalysisServices.AdomdClient.AdomdComman d.ExecuteCellSet() "


tia






Reply With Quote
  #4  
Old   
Graham Lloyd
 
Posts: n/a

Default Re: MDX Compatibility Property - 07-05-2006 , 07:45 PM



Akshai - some more info for you.....

I have also tried installing the cumilitive patch (9.0.2153) and still have
the same problem. I also found that I can perform a count() on the
AllMembers and get the correct result.

This is my connectionString if case that provides you with any other clues
Data Source=myServer;MDX Compatibility=2;Integrated
Security=SSPI;ConnectTo=9.0;Provider=MSOLAP.3;SSPI =NTLM;Catalog=Sample Data

Can you give me an indication of whether you think this is likely to be a
bug or a design issue? The dimension browser forms an integral part of our
application, so I really need to get this fixed asap. Are you (or anyone
else reading this) able to test this scenario?

tia

Graham



"G_NoSpam" <gilly1409 (AT) hotmail (DOT) com> wrote

Quote:
Hi Akshai - thatnks for the response

We are using SP1. Any other ideas? All the other dimesnions that don't
have hidden members work ok!






"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote in message
news:O3Vjo0HoGHA.764 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
Are you on SP1 of AS? I recall a bug was fixed for this in SP1...

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

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.

"Graham Lloyd" <gilly1409 (AT) hotmail (DOT) com> wrote in message
news:%23ZLFlR9nGHA.4340 (AT) TK2MSFTNGP05 (DOT) phx.gbl...
Hi

We have a ragged dimension where we hide the members if they have an
empty name. I found some documentation here (
http://msdn2.microsoft.com/en-us/library/ms365406.aspx ) on how to
handle them. We have a custom web browser to view the members in the the
dimensions/hierarchies and use MDX to retrieve the members. When we set
the MDX Compatibility property to 2, the members are presented correctly
with the blank members ommitted from the list.

This all works fine but now the following MDX now fails with Exception
"Internal error: An unexpected exception occured."

SELECT [dimension].[hierarchy].members ON 0, {} ON 1 FROM [cubeName]

or

SELECT [dimension].[hierarchy].AllMembers ON 0, {} ON 1 FROM [cubeName]

If Compatibility is not set to 2 in the connection string the above
statements work.

Any ideas why this now doesn't work or an alternative way to retrieve
all the members from a hierarchy? We are using SSAS 2005 with ADOMD.net
v9.

Full stack trace follows

" at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.XmlaClientProvider.Microsoft.AnalysisServices .AdomdClient.IExecuteProvider.ExecuteMultidimensio nal(ICommandContentProvider
contentProvider, AdomdPropertyCollection commandProperties,
IDataParameterCollection parameters)\r\n at
Microsoft.AnalysisServices.AdomdClient.AdomdComman d.ExecuteCellSet() "


tia








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

Default Re: MDX Compatibility Property - 07-07-2006 , 11:17 PM



It looks like a bug.

Testing this by itself probably won't show me the issue because I expect
there must be something specific in your dimension/cube that causes this
problem. I would suggest contacting support and opening a case for the
problem...

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

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.

"Graham Lloyd" <gilly1409 (AT) hotmail (DOT) com> wrote

Quote:
Akshai - some more info for you.....

I have also tried installing the cumilitive patch (9.0.2153) and still
have the same problem. I also found that I can perform a count() on the
AllMembers and get the correct result.

This is my connectionString if case that provides you with any other clues
Data Source=myServer;MDX Compatibility=2;Integrated
Security=SSPI;ConnectTo=9.0;Provider=MSOLAP.3;SSPI =NTLM;Catalog=Sample
Data

Can you give me an indication of whether you think this is likely to be a
bug or a design issue? The dimension browser forms an integral part of our
application, so I really need to get this fixed asap. Are you (or anyone
else reading this) able to test this scenario?

tia

Graham



"G_NoSpam" <gilly1409 (AT) hotmail (DOT) com> wrote in message
news:%23PgDfFIoGHA.4464 (AT) TK2MSFTNGP04 (DOT) phx.gbl...
Hi Akshai - thatnks for the response

We are using SP1. Any other ideas? All the other dimesnions that don't
have hidden members work ok!






"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote in message
news:O3Vjo0HoGHA.764 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
Are you on SP1 of AS? I recall a bug was fixed for this in SP1...

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

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.

"Graham Lloyd" <gilly1409 (AT) hotmail (DOT) com> wrote in message
news:%23ZLFlR9nGHA.4340 (AT) TK2MSFTNGP05 (DOT) phx.gbl...
Hi

We have a ragged dimension where we hide the members if they have an
empty name. I found some documentation here (
http://msdn2.microsoft.com/en-us/library/ms365406.aspx ) on how to
handle them. We have a custom web browser to view the members in the
the dimensions/hierarchies and use MDX to retrieve the members. When we
set the MDX Compatibility property to 2, the members are presented
correctly with the blank members ommitted from the list.

This all works fine but now the following MDX now fails with Exception
"Internal error: An unexpected exception occured."

SELECT [dimension].[hierarchy].members ON 0, {} ON 1 FROM [cubeName]

or

SELECT [dimension].[hierarchy].AllMembers ON 0, {} ON 1 FROM [cubeName]

If Compatibility is not set to 2 in the connection string the above
statements work.

Any ideas why this now doesn't work or an alternative way to retrieve
all the members from a hierarchy? We are using SSAS 2005 with ADOMD.net
v9.

Full stack trace follows

" at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.XmlaClientProvider.Microsoft.AnalysisServices .AdomdClient.IExecuteProvider.ExecuteMultidimensio nal(ICommandContentProvider
contentProvider, AdomdPropertyCollection commandProperties,
IDataParameterCollection parameters)\r\n at
Microsoft.AnalysisServices.AdomdClient.AdomdComman d.ExecuteCellSet() "


tia










Reply With Quote
  #6  
Old   
Graham Lloyd
 
Posts: n/a

Default Re: MDX Compatibility Property - 07-08-2006 , 03:11 AM



Thanks for the response Akshai

I have found the specific issue and managed to find a work around. The exact
problem was not with AllMembers but any cellset that contained specific
members. in particular, members whose top level had an empty name. We had
need for members with no children to appear at level0 alongside other
standard members. To work around the 'bug', presiming it is, was to change
the members with no name to members of the same name as the base level. Then
set the property 'hideMemberIf' property to be same as parent.

Should I still report the original issue as a bug to Microsoft Support? If
so what channel should I use.

many thanks

Graham



"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote

Quote:
It looks like a bug.

Testing this by itself probably won't show me the issue because I expect
there must be something specific in your dimension/cube that causes this
problem. I would suggest contacting support and opening a case for the
problem...

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

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.

"Graham Lloyd" <gilly1409 (AT) hotmail (DOT) com> wrote in message
news:eo6LjVJoGHA.3348 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
Akshai - some more info for you.....

I have also tried installing the cumilitive patch (9.0.2153) and still
have the same problem. I also found that I can perform a count() on the
AllMembers and get the correct result.

This is my connectionString if case that provides you with any other
clues
Data Source=myServer;MDX Compatibility=2;Integrated
Security=SSPI;ConnectTo=9.0;Provider=MSOLAP.3;SSPI =NTLM;Catalog=Sample
Data

Can you give me an indication of whether you think this is likely to be a
bug or a design issue? The dimension browser forms an integral part of
our application, so I really need to get this fixed asap. Are you (or
anyone else reading this) able to test this scenario?

tia

Graham



"G_NoSpam" <gilly1409 (AT) hotmail (DOT) com> wrote in message
news:%23PgDfFIoGHA.4464 (AT) TK2MSFTNGP04 (DOT) phx.gbl...
Hi Akshai - thatnks for the response

We are using SP1. Any other ideas? All the other dimesnions that don't
have hidden members work ok!






"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote in
message news:O3Vjo0HoGHA.764 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
Are you on SP1 of AS? I recall a bug was fixed for this in SP1...

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

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.

"Graham Lloyd" <gilly1409 (AT) hotmail (DOT) com> wrote in message
news:%23ZLFlR9nGHA.4340 (AT) TK2MSFTNGP05 (DOT) phx.gbl...
Hi

We have a ragged dimension where we hide the members if they have an
empty name. I found some documentation here (
http://msdn2.microsoft.com/en-us/library/ms365406.aspx ) on how to
handle them. We have a custom web browser to view the members in the
the dimensions/hierarchies and use MDX to retrieve the members. When
we set the MDX Compatibility property to 2, the members are presented
correctly with the blank members ommitted from the list.

This all works fine but now the following MDX now fails with Exception
"Internal error: An unexpected exception occured."

SELECT [dimension].[hierarchy].members ON 0, {} ON 1 FROM [cubeName]

or

SELECT [dimension].[hierarchy].AllMembers ON 0, {} ON 1 FROM
[cubeName]

If Compatibility is not set to 2 in the connection string the above
statements work.

Any ideas why this now doesn't work or an alternative way to retrieve
all the members from a hierarchy? We are using SSAS 2005 with
ADOMD.net v9.

Full stack trace follows

" at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.XmlaClientProvider.Microsoft.AnalysisServices .AdomdClient.IExecuteProvider.ExecuteMultidimensio nal(ICommandContentProvider
contentProvider, AdomdPropertyCollection commandProperties,
IDataParameterCollection parameters)\r\n at
Microsoft.AnalysisServices.AdomdClient.AdomdComman d.ExecuteCellSet() "


tia












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

Default Re: MDX Compatibility Property - 07-10-2006 , 03:35 PM



Either Microsoft Support (based on your support contract situation) or you
could use the Microsoft Connect website (http://connect.microsoft.com) to
send feedback about SQL Server...

HTH,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

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.

"Graham Lloyd" <gilly1409 (AT) hotmail (DOT) com> wrote

Quote:
Thanks for the response Akshai

I have found the specific issue and managed to find a work around. The
exact problem was not with AllMembers but any cellset that contained
specific members. in particular, members whose top level had an empty
name. We had need for members with no children to appear at level0
alongside other standard members. To work around the 'bug', presiming it
is, was to change the members with no name to members of the same name as
the base level. Then set the property 'hideMemberIf' property to be same
as parent.

Should I still report the original issue as a bug to Microsoft Support? If
so what channel should I use.

many thanks

Graham



"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote in message
news:uPoJrVkoGHA.148 (AT) TK2MSFTNGP04 (DOT) phx.gbl...
It looks like a bug.

Testing this by itself probably won't show me the issue because I expect
there must be something specific in your dimension/cube that causes this
problem. I would suggest contacting support and opening a case for the
problem...

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

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.

"Graham Lloyd" <gilly1409 (AT) hotmail (DOT) com> wrote in message
news:eo6LjVJoGHA.3348 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
Akshai - some more info for you.....

I have also tried installing the cumilitive patch (9.0.2153) and still
have the same problem. I also found that I can perform a count() on the
AllMembers and get the correct result.

This is my connectionString if case that provides you with any other
clues
Data Source=myServer;MDX Compatibility=2;Integrated
Security=SSPI;ConnectTo=9.0;Provider=MSOLAP.3;SSPI =NTLM;Catalog=Sample
Data

Can you give me an indication of whether you think this is likely to be
a bug or a design issue? The dimension browser forms an integral part of
our application, so I really need to get this fixed asap. Are you (or
anyone else reading this) able to test this scenario?

tia

Graham



"G_NoSpam" <gilly1409 (AT) hotmail (DOT) com> wrote in message
news:%23PgDfFIoGHA.4464 (AT) TK2MSFTNGP04 (DOT) phx.gbl...
Hi Akshai - thatnks for the response

We are using SP1. Any other ideas? All the other dimesnions that don't
have hidden members work ok!






"Akshai Mirchandani [MS]" <akshaim (AT) online (DOT) microsoft.com> wrote in
message news:O3Vjo0HoGHA.764 (AT) TK2MSFTNGP03 (DOT) phx.gbl...
Are you on SP1 of AS? I recall a bug was fixed for this in SP1...

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

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.

"Graham Lloyd" <gilly1409 (AT) hotmail (DOT) com> wrote in message
news:%23ZLFlR9nGHA.4340 (AT) TK2MSFTNGP05 (DOT) phx.gbl...
Hi

We have a ragged dimension where we hide the members if they have an
empty name. I found some documentation here (
http://msdn2.microsoft.com/en-us/library/ms365406.aspx ) on how to
handle them. We have a custom web browser to view the members in the
the dimensions/hierarchies and use MDX to retrieve the members. When
we set the MDX Compatibility property to 2, the members are presented
correctly with the blank members ommitted from the list.

This all works fine but now the following MDX now fails with
Exception "Internal error: An unexpected exception occured."

SELECT [dimension].[hierarchy].members ON 0, {} ON 1 FROM [cubeName]

or

SELECT [dimension].[hierarchy].AllMembers ON 0, {} ON 1 FROM
[cubeName]

If Compatibility is not set to 2 in the connection string the above
statements work.

Any ideas why this now doesn't work or an alternative way to retrieve
all the members from a hierarchy? We are using SSAS 2005 with
ADOMD.net v9.

Full stack trace follows

" at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.XmlaClientProvider.Microsoft.AnalysisServices .AdomdClient.IExecuteProvider.ExecuteMultidimensio nal(ICommandContentProvider
contentProvider, AdomdPropertyCollection commandProperties,
IDataParameterCollection parameters)\r\n at
Microsoft.AnalysisServices.AdomdClient.AdomdComman d.ExecuteCellSet()
"


tia














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.