I have a tricky question and I do not exactly know where to find relevant information to this.
I have SQL Server 2014 Enterprise installed on a database server. On this server there exist multiple databases, some belong to us and some to other companies.
My concern is with cache memory. I have a basic understanding of how SQL Server uses cache memory to retrieve data pages fast. You run a query, and usually, data pages get loaded to the cache and with repeatable calls, it gets results from this.
But... our application is highly used in usual working hours by our customers but at night there are always maintenance tasks going on. I am assuming (please tell me if I am wrong) that during the day, the cache gets loaded with useful data pages, but at night it is deleted because of the maintenance tasks, and so the next day, when customers start doing transactions, data pages have to be again loaded into the cache first, which takes time and slows a lot of things down.
So, can I somehow prove if that happens?
If yes, can I manage it? Such as somehow telling SQL Server to not load into cache?
I would be grateful for some specific articles discussing this topic. I could not find any, or better say, I do not know how to name this problem.