Scott,
That is great advice, thanks. The application mainly consistently saves data and there is a web application that also saves and reads. But I don’t think we have any large queries that could fill up the buffer pool.
This is backed up by checking the evicted without access value:
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
1 row in set (0.16 sec)
I don’t know why it is repeated 8 times, but anyway.
We do have more RAM available but not the 70GB (30 x 1.1 x 2) that I have read is ideal. I will monitor the evicted without access value like you suggested and keep an eye out for bad queries.
Thanks again,
Stephen