When
a query requires additional memory resources, the number of pages that it gets is determined
partly by the Min Memory Per Query option.
This
option is relevant for sort operations that you specifi cally request
using an ORDER BY clause, and it also applies to internal memory needed by
merge-join operations and by hash-join and hash-grouping operations. This
configuration option allows you to specify a minimum amount of memory (in
kilobytes) that any of these operations should be granted before they are
executed. Sort, merge, and hash operations receive memory in a very dynamic
fashion, so you rarely need to adjust this value.
In fact, on larger machines,
your sort and hash queries typically get much more than the Min Memory Per
Query setting, so you shouldn’t restrict yourself unnecessarily. If you need to
do a lot of hashing or sorting, however, and you have few users or a lot of
available memory, you might improve performance by adjusting this value. On
smaller machines, setting this value too high can cause virtual memory to page,
which hurts server performance.
http://www.mybasicknowledge.com/2012/09/sql-server-configurations-and.html
