Disable Sql 2008 Caching?

Question

I have an application that makes different requests with different results, so caching in my case is harmful.

This means that there is no general data that sql can extract from it to get the result from memory directly, and not to access the hard drive.

Answer 1

From your comments, it sounds as if you do not want SQL to use a lot of memory, because you feel that it makes no sense, since any queries you run are random.

First, this memory is probably used to store indexes and query plans, not the actual data that you want to return, so you will probably find that this cache is much more useful than you think.

Secondly, it is unlikely that sql using this amount of memory will result in poor performance on a truly random invisible query. If SQL Server needs to go to disk to get any information, then the amount of memory it uses is hardly relevant.

However, you can reduce the amount of memory that SQL Server uses. (I don't know where the option is in SQL 2008, but I assume it is pretty similar). In Management Studio, right-click on the server and do "Properties". There will be a memory page. Here you can select the minimum and maximum values ​​that SQL will use. This will effectively limit any sql caching based on your values, not the limitations of physical servers.

I really do not think that you will see at least some profit from productivity. In my experience, SQL is always the best thing to do.

Answer 2

Your question is incorrect: caching means that the data is stored in memory and avoids access to the disk.

In any case, caching SQL Server is not harmful. There are always exceptions for pedants, but before that happens, you have to seriously inflate the code and configuration.

Answer 3

Disabling (or attempting to disconnect) SQL Server Caching does not properly address the issue. If data is cached at your data layer level, you should update it there. SQL Server will never serve outdated data.