This is to share some information in regards to memory.

Yesterday, I finally obtained an increase of memory from 32 GB to 64 GB. I was able to see how SQL Server handles that. It took several hours until SQL Server cached an enormous amount of data into the full memory location available. This worked. It was interesting to see how that worked over several hours. At first, I did not see any difference compare to when I was running at 32 GB. Because, SQL Server cannot cache it out in a matter of seconds. We are talking about an enormous amount of data here. But, overnight, it started to go over the 32 GB limit. This morning, I see that it has cached 64 GB of data.

I was analyzing my numbers based on a very intensive operation I am doing. So far, my process is targeting as being run around 54 hours instead of 78.

Basically, if a reboot is done, or if a start of service is done, the memory will have to be rebuilt again. But, once the daily operations are in effect, depending on how it sees what has to be cache, after a certain number of hours, it will show a boost of performance at various levels as more data has been uploaded to memory.

In my case, this is close to 20 hours. This is about the time it took to cache the data. YMMV however based on the queries and this is normal. In my case, this was tested using a very intensive program doing pretty much the same queries. In real life, from the Web application, this may take longer as the range of various queries will vary.