i can't give a general answer, because the memory request is dependent on your type of query and how your datas are structered and stored (exist there indexes for your query or must the server scan the table).
The data / indexes are stored in pages wich has 8k. So when the server execute your query and must only make 6 reads to get the result set, he load 6x8k in memory. But is your question bad (or you have no index which can be used) and you have, for example, 5.179.823 Reads x 8K (Page) = 41.438.584KB = about 40GB ](*,)
oh, he mean the option in SQlServer properties. Sorry i misunderstood this.
That's how I read the question since there's a SQL property by that exact name. I've never had a reason to use that property. I've always just let SQL manage its memory.
IMHO it's only feasible to adjust this setting if you receive data-result-sets of a (more or less constant) size. As we have in NAV quite different result-sets - from 0 to xMillion records - I think it's better to leave it to the standard default value ...
Actually I never had reason to change it so far.
Comments
The data / indexes are stored in pages wich has 8k. So when the server execute your query and must only make 6 reads to get the result set, he load 6x8k in memory. But is your question bad (or you have no index which can be used) and you have, for example, 5.179.823 Reads x 8K (Page) = 41.438.584KB = about 40GB ](*,)
That's how I read the question since there's a SQL property by that exact name. I've never had a reason to use that property. I've always just let SQL manage its memory.
Actually I never had reason to change it so far.
NAV/SQL Performance Optimization & Troubleshooting
STRYK System Improvement
The Blog - The Book - The Tool