If your SQL Server is experiencing memory bottlenecks, consider these possible solutions:
· Add more physical RAM. If you are already at 2GB of physical RAM and are still having a memory problem, consider upgrading to SQL 2000 or 2005 Enterprise Edition, which can support up to 64GB of physical RAM using the AWE memory extension.
· Consider upgrading to the 64-bit version of SQL Server 2000 or 2005.
· Ensure that SQL Server is the only application running on the server (other than server management utilities).
· Remove or disable all unnecessary services.
· Ensure SQL Server is running as a member server (not a domain controller).
· Configure SQL Server to allocate memory dynamically (the default), don’t hard code how much RAM SQL Server is allocated (unless using AWE memory)
· Be sure that data pages don’t have too much empty space, either because the fillfactor is too high, or because of page fragmentation. Extra space on database pages wastes space in the buffer cache.
· Turn off virus checking software.
[6.5, 7.0, 2000, 2005] Updated 6-20-2005
*****
If your SQL Server is experiencing network bottlenecks, consider these possible solutions:
· Add faster network cards.
· Add additional network cards.
· Use the latest network card drivers.
· Server network card(s) should be attached to switches.
· Network cards should be running in full duplex mode.
· Manually hard code network cards to match the speed of the switch they are connected to. Don’t use auto-detect sensing methods.
· Tune your application so that it does not require unnecessary network trips. Do this by returning only the required data and by using stored procedures.
· Remove all unnecessary network protocols from the server.
· Ensure that SQL Server is the only application running on the server (other than server management utilities).
· Remove or disable all unnecessary services.
· Use TCP/IP as the network library on the client and server.
[6.5, 7.0, 2000, 2005] Updated 6-20-2005
]]>