Post reply

SQL 2005 x86 on Windows Server 2003 Standard Edition

  • September 2, 2008 at 12:07 am

    #192984

    Hi All,

    I would appreciate some feedback to the following;

    Current Setup

    WIN Server 2003 Standard with 4GB memory

    SQL 2005 Standard SP2 (not sure which cumulative update of SP2 tho)

    ***...Only OS and SQL runs on this machine...***

    Database:

    master/model on C

    Data on D (SCSI 15000rpm RAID 10)

    Log on E (SCSI 15000rpm RAID 1)

    Tempdb on F (SCSI 15000RPM RAID 1)

    During monitoring the SQL uses upto 1.72GB memory. I know it also uses 300MB memory for hidden processes, therefore it is using 2GB memory.

    The drives are all fine except F which gets hammered with avg disk queue way up high for very short periods.

    Do the temp files get hammered if the memory is maxed out?

    Also, I simply want to enable 3GB memory....???

    (Later I may also add another 2 or 4GB memory and use it for SQL too...)

    Can someone please tell me clearly how to do this?

    Thankyou.

    Notes: I enabled AWE and set Max Memory to 3072, ran a process to test and the system consumed the memory very slowly??? I turned off AWE and ran the process again and it flew and also consumed the memory right up to 1.7GB pretty quickly. Obviously the AWE setting affected this. Therefore I hope the solution to using 3GB does not involve setting AWE because this will mean users processes run slowly. Is that correct?

    Also I have heard of the 3gb switch in boot.ini but I am not sure exactly the process I should take to enable 3gb...

    I look forward to everyone's feedback.

    Newbie # 0049876D6

  • September 2, 2008 at 5:11 am

    #865922

    Hi All,

    thanks for the input! Much appreciated.

    I've set the /3GB and we'll see how the utillisation goes.

    Cheers

    Kris Aus

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply