This project has moved and is read-only. For the latest updates, please go here.

Memory Leak on repetedly deploy MDX Script

Topics: Standing Discussions
Jul 8, 2015 at 8:13 AM
Observed and reproduced the following scenario.
A Cube has calculated measures and scopes, about 15 script items total. I repeatedly modified calculated members and deployed MDX script.
After about 30 MDX script deploys amount of RAM used increased from 0.8 GB to 2 GB. No additional actions in BIDS like cube build and deploy or modifications were performed.
Jul 8, 2015 at 1:57 PM
What version of SSDT or BIDS? About how long did this repro take? 30 seconds? Hours?

Thanks for reporting!
Jul 8, 2015 at 3:15 PM
Information on setup and process.
OS - MS Windows Server 2003, BIDS - MS BIDS 2008 (from MS SQL 2008 x64 setup), BIDS helper -
Process - editing cube script. Whole project is quite big, asdatabase file is approx. 29 MB. At start, devenv.exe takes about 500 MB, after each cube save and MDX processing - memory used increases by 10-20 MB. Interesting fact - after MDX script deploy is finished (according to progress bar below), BIDS stays not responding to user actions for 10-15 seconds, utilizing 1 CPU core.
After several hours of tuning MDX scripts with save and deploy, amount of RAM used by devenv.exe raised up to 1,8 GB.

Thank you for your assistance!
Jul 9, 2015 at 5:09 AM
Can you do me a favor? Instead of doing a Deploy MDX Script, can you just make a minor change then do a Build on the project over and over again? If you can reproduce the memory leak than that's out of BIDS Helper control. If not we can see if it's our code.

After the Deploy MDX script completes it triggers a Build. The reason is that some users were deploying small changes to the MDX script then running the AS Deployment Wizard without doing a Build. The wizard deployed a stale copy of the asdatabase file. So we decided it was safest to trigger a Build after you deploy the MDX script.