Re: AS2K Performance Problem
- From: Darren Gosbell <xxx@xxxxxxx>
- Date: Wed, 5 Oct 2005 16:32:42 +1000
> I do rename msmdvldm.exe and then everything is work fine.
msmdvldm.exe is the "Very Large Dimension Manager", by default it only
kicks in when your dimensions exceed 67108864 bytes, which would happen
in your case if your members were storing more than about 134 bytes
each.
Rather than renaming (therefore totally disabling the VLDM) another
option would be to increase the VLDMThreashold. You change this via the
following registry key.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\CurrentVersion
\VLDMThreshold
It accepts a maximum value of 4294967295.
The VLDM incurs a performance penalty as it has to communicate across
process boundaries, but I don't know why you would see such a dramatic
performance hit.
--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell
.
- References:
- Re: AS2K Performance Problem
- From: anote_un
- Re: AS2K Performance Problem
- From: anote_un
- Re: AS2K Performance Problem
- Prev by Date: Re: Unable to set intrinsic "DESCRIPTION" member property
- Next by Date: Re: UPDATE CUBE Reference
- Previous by thread: Re: AS2K Performance Problem
- Next by thread: Distinct Count based on another measure
- Index(es):
