It is healthy behavior if a QlikView server eats up 70% of the memory of a server after some time. There is nothing wrong with that. A common misconception is thinking there is a memory leak or anything wrong.
If users can make pivot tables with a huge amount of dimensions and calculations being used, add a calculation condition to limit this. Though usually these huge things take forever to calculate, so it will run into calculation time-out after a minute anyway.
Are you running a dedicated server? If not, now would be a right time to start doing that .
We run a dedicated server, and including condition is in the works (should be deployed within 1 month).
I was looking for a QlikView software solution, I know it exists in some other BI platforms and was hoping to find something like that in QlikView. I would like qlikview to stop (present user with an error) when Virtual Memory limit has been exceeded. Other option would be to use something like 'incremental fetch' - user would be able to go into 'deep dive' tab, but would be presented with a limited no. of rows (just like queries work in TOAD with default settings).
The problem is that users are careless and crash the server by overloading it.