RATE THIS ANSWER
0
Click to Vote:
- 0
0
Last Answered:
Jul 14 2008 10:43 PM GMT
by Mrdenny
The goal with SQL Server is to not use the page file at all. If SQL needs to page data out then additional RAM should be installed as accessing data within the page file is typically as slow or slower then accessing it within the database files directly.
If you have SQL Server 2005 Enterprise Edition you can set the Lock Pages in memory setting to prevent SQL Server from using the page file, which is typically recommended. SQL Server 2005 Standard edition and below do not recognize this setting.
It's currently recommended that you set your maximum memory setting for 75% of your physical memory. Another maximum memory setting is that you set the setting for 2-4 Gigs below your physical memory. You'll need to try both settings and see which works better for you under your workload.
Memory, Database, Windows Server 2003, SQL Server 2005, Server management
I have a Windows 2003 Enterprise 64-bit server running SQL 2005 x64 with 32GB RAM. The SQL database is acting as a transaction database. What is the best way to manage memory on this server? Should I adjust the paging file? If so, to what? Any ideas are appreciated! 
