Hi,

We have a parent-child dimension built from a table that
has approx. 104,000 rows in it. This dimension has been
processing fine for about 3 months until earlier this
month. All of the AS shared dimensions,including this one
are processed with one DTS script step. This step started
failing and/or hanging.

After reading KB article 294285 I tried a full processing
of the dimension by itself. The processing caused AS to
max out the memory allocated to it and it hung. CPU time
falls back to 0-4% activity after the AS hangs. During
this process I had PerfMon loaded up looking for VLDM
activity and requests. (QueryDim:TotalVLDMRequests and
QueryDim: VLDMRequests/Second) Both counters remained
flat. There was also no VLDM process running under task
manager's process pane.

I checked the VLDMThreshold registry entry and it was set
for 64MB. The whole cube this dimension is processed into
is 26MB (MOLAP).

My suspicion is with the depth of this parent-child tree.
Is there an undocumented upper limit on the depth of a
parent-child tree? The source data this is coming from
does not have a circular reference or anything like that.

As another test I created another dimension from this same
source table as a 3-level star-schema shared dimension and
it processed fine. I tied it to a cube and again,
everything processed fine. This only fails if I make the
dimension parent-child.

Any advice to troubleshoot this problem would be
appreciated.

Thanks,

--Debora Orf