msmdqlog.mdb bug - "dataset" field only 64 chars
Marco Russo
Table QueryLog has a "dataset" field of 64 characters.
If you have a cube with more than 64 dimensions, Analysis Services
doesn't log anything for query made to that cube, and write an entry
in Application log of Windows.
In other word, usage log for cube with more than 64 dimension doesn't
work.
I expanded this field to 128 characters, and now everything works
fine.
Obviously SQL2KAS SP2 already installed.
I searched on the web and I haven't found any info about that.
Is this really a bug?
Any other info about that?
Thanks in advance.
Marco
Tim Harris
64 Dimensions?
Perhaps it is a bug, but that seems like way too many dimensions in one cube
to me.
"Marco Russo" <marco...@loader.it> wrote in message
news:a017eee.03010...@posting.google.com...
Rita Nikas [MSFT]
I'm looking into this. I hope to have an update for you no later than
tomorrow.
Sincerely,
Rita Nikas, MCSE MCDBA
Product Support Services
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Subject: msmdqlog.mdb bug - "dataset" field only 64 chars
| Date: 9 Jan 2003 06:47:29 -0800
Rita Nikas [MSFT]
Yes, this is a known issue (KB is pending).
Sincerely,
Rita Nikas, MCSE MCDBA
Product Support Services
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Subject: msmdqlog.mdb bug - "dataset" field only 64 chars
| Date: 9 Jan 2003 06:47:29 -0800
|
Marco Russo
I know that a cube with more than 20 dimension is nearly unusable with
a standard client.
But I have a customer with very specific needs and a custom client.
The presence of all these dimension make some kind of analysis really
simple with that client. Indeed, many of these dimensions are virtual
dimension, but the log treat these like standard dimensions.
The official limit of Analysis Services is 128 dimensions, and as MS
kindly answered in a following message, the MSMDQLOG.MDB structure
does not allow to use more than 64.
I think that those 2 or 3 people around the world with the same
problem will be happy to find this thread with Google :-)
Marco
"Tim Harris" <tha...@oneprice.com> wrote in message news:<#S27LoAuCHA.2540@TK2MSFTNGP10>...
Kornel
Hi Marco,
It looks like I am one of this "2 or 3 people around the word" :) with
the same problem as You. This is not a marginal problem because of
virtual dimmensions that we use. Thanks for oportunity to find here
solutution to this problem.
Best rgds.
Kornel.
Originally posted by Marco Russo
> Tim,
>
> I know that a cube with more than 20 dimension is nearly unusable with
> a standard client.
> But I have a customer with very specific needs and a custom client.
> The presence of all these dimension make some kind of analysis really
> simple with that client. Indeed, many of these dimensions are virtual
> dimension, but the log treat these like standard dimensions.
> The official limit of Analysis Services is 128 dimensions, and as MS
> kindly answered in a following message, the MSMDQLOG.MDB structure
> does not allow to use more than 64.
> I think that those 2 or 3 people around the world with the same
> problem will be happy to find this thread with Google :-)
>
> Marco
>
> "Tim Harris" wrote in message news:news:...
> > 64 Dimensions?
> > Perhaps it is a bug, but that seems like way too many dimensions
> in one cube
> > to me.
> >
> > "Marco Russo" wrote in message
> > news:a017eee.03010...@posting.google.com"]news-
> :a017eee.03010...@posting.google.com[/url]...
--
Posted via http://dbforums.com