Hello,

I've searched the archives and haven't found anything of use. I hope
that I have the right newsgroup and that someone can help.

I have a number of cubes (developed by partners of the company I work
for) that are fairly big in structure (30-80 dimensions), although
there isn't that much data in them yet. When these are browsed and
navigated through in Analysis Manager, we are getting an error in the
application part of the event log on the server machine, at 30 second
intervals while the navigation is in progress (i.e. when changing
context). The source is "MSSQLServerOlapService". The error is as
follows:

Relational data provider reported error: [The field is too small to
accept the amount of data you attempted to add. Try inserting or
pasting less data.;3163].

There doesn't appear to be any noticable affect in Analysis Manager -
the browsing and navigation works OK. However, there is a separate
issue that may be related: we use XML for Analysis, and from a
separate machine fire off MDX queries to return small result sets.
When we do this with the largest cube, we get DLLHOST.exe grabbing all
available CPU processing time and gobbling up more and more memory for
about five minutes, before it returns the memory it took up and
settles down again, with the (small) results returned successfully.

Does anyone have any ideas about what might be happening?

We use SQL Server 2000 and its equivalent Analysis Server, and have
SP3 applied for both. The server machine has Windows 2000 installed.

--
Neil Brown
google at highmount dot demon dot co dot uk

When you query analysis services database, it tries to save usage
information into database.
File where it saves data is: c:\Program Files\Microsoft Analysis
Services\Bin\msmdqlog.mdb
In analysis services properties you can setup how often you want to save
queries, default value 10 - every 10th query is saved.
When I say "saved query" I mean it saves information at what level each
dimension was queried.
Now when you have cube with large set of dimensions, it cannot save record,
as it expects fields with max 64 characters and gets bigger field. For some
reason I get same problem with 57dimension (most of them virtual).
Anyway, you can ignore this if you do not plan to do usuage based
optimization.
You could disable loging in Analysis services parameters: Right mouse click
on the server name in analysis manager, properties, Logging...


Regards,

Vidas M.


"Neil Brown" <google (AT) highmount (DOT) demon.co.uk> wrote

Many thanks for solving the mystery! I was worried in case it turned
out to be some fundamental problem with the cubes. I increase the size
of the Dataset text field in the QueryLog table of the DB you
mentioned below, and the event log error stopped appearing - plus,
queries on the cube in question started appearing in the query log
database.

--
Neil Brown

"Vim" <Vim (AT) Me (DOT) com> wrote