Hi Cathal,

Thanks for the tip!

I just checked the SQL server online books again and you are right that if a query requires more memory it will be given more memory. The setting just guarantees that when a query is run it will get that amount of memory, thus resulting in a smoother running DNN, when alot of queries are run concurrently, as is the case with DNN and many users online.

I believe that each query being fired doesn't need to check SQL server first if the default 1024kb memory size is sufficient enough and then be assigned more to run properly. It just has more then enough in the first place, thus not bothering SQL server to assign more memory to it, and then free it up again later.  In most cases, these would be minor operations for SQL server.

But when DNN is hit on by many users, causing many queries to fire al these 'minor' operations become many operations, potentially causing slowness. The amount of slowness depending on the amount of users hitting the DNN install concurently.

But this is just my brain experiment on how SQL might work regarding DNN and in general and I found that just giving queries lots of memory from the start smoothed DNN performance quite a bit. Although I admit that 32Mb is a bit over the top...

Again thanks for the tip I'll keept it in mind and try it out soon!