I have an complex MDX statement that is using Linked Server to an AS database
that is embedded in a stored procedure.

I have been able to get it to work fine in my dev environment, but in QA we
seem to have an issue when the data being returned passes 200+ rows (it
appears to be linked to the amount of data).

After a certain point all of the data from the openquery statement is
replaced with "-2,147,467,000.000" or some variation thereof. This is a
wholesale change. Once the data starts being replaced it is replaced for all
the rows from that point forward.

I have had no luck finding a difference between the systems. If you are
aware of something to check please let me know.

Thanks.

Here is how I solved this issue:
I eventually solved the problem. How the solution works is beyond me at
this point. As mentioned the problem appeared in a calculated member in the
openquery statement that used a sum of calculated member (from the cube) in a
set built in the openquery statement. The calculated member in the cube was
a tuple with a measure in it. When I moved the tuple to the calculated
member in the openquery, my issue went away.

Don't know why this worked differently. Would be happy to hear any reasons
this may be true.

Thanks,
Steve

"Steve Hughes" wrote: