SQL Server Performance

Need advice on configuring new server (8 gig ram)

Discussion in 'Performance Tuning for Hardware Configurations' started by kenp2600, May 22, 2007.

  1. kenp2600 New Member

    In the next 10 days my new sql server should arrive. It will be running Windows Server 2003 and SQL 2000.

    The server has 8 Gig of RAM and I would like some advice on how to configure the OS/SQL to get the most out of the 8 gig.

    Also, as a side note, how should I configure my pagefile? I will have 2 Raid arrays to work with, a Raid 1 for OS and Log Files, and a Raid 5 for Data files.

    Thank you in advance.
  2. satya Moderator

    The general recommendation for PF will be initial and maximum page file size is equal to 1.5 times the amount of RAM, up to maximum limit of 4,095 MB. This means that the largest paging file
    size per volume that you can set is 4,095 MB.

    To prevent page file fragmentation, it is recommended that you set the paging file size initial and maximum values to be the same value. If you decrease the size of either the initial or maximum page file settings, you must restart your computer to see the effects of those changes. Increases typically do not require a restart.

    Fyi KBAhttp://support.microsoft.com/?id=197379

    Satya SKJ
    Microsoft SQL Server MVP
    Writer, Contributing Editor & Moderator
    This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
  3. bradmcgehee New Member

    Also check outhttp://www.sql-server-performance.com/awe_memory.asp

    Don't be surprised if your SQL Server instance does not use all of the memory you have. SQL Server will use as much as it needs (assuming it has enough). But many people are surprised how little memory SQL Server really needs. For example, I have a client that has a 40GB database, but SQL Server only uses about 130 MB out of an available 8 GB on the server. For whatever reason, this particular production database can maintain a 99%+ buffer hit cache ratio with only 130 MB of RAM, and it runs as fast as can be expected. The rest of the RAM is never used.

    Brad M. McGehee, SQL Server MVP

Share This Page