Tuesday, May 3, 2011

Memory Usage

Hi Friends,

Can somebody please, let me know that what are the most memory consuming reasons in SQL SERVER 2005?

Please, let me know.

Thanks,

From stackoverflow
  • Buffer pool for mainly data, plans, locks

    Can you add some background please?

  • The SQL Rocks article Memory Use in SQL Server will probably answer your question.

    I think this is one of the important parts:

    SQL Server's caching behavior is the reason for the substantial memory use. This is by design and is not a bug, memory leak nor incorrect configuration. This is by design and is not a bug, memory leak nor incorrect configuration. Every time SQL Server needs to read a page from disk it caches the page in memory so that the slow disk operation will be unnecessary should SQL Server need that page again. Every time SQL Server needs to read a page from disk it caches the page in memory so that the slow disk operation will be unnecessary SQL Server should need that page again.

    SQL Server is just memory hungry. The more memory you give it, the more it will use. SQL Server should probably always be run on its own server if it is doing anything non-trivial. In other words, don't install SQL Server on your domain controller, file server or source control repository (unless your source control repository uses SQL Server).

0 comments:

Post a Comment