Post reply

sql server is not using more than 3gb causing performace issues.

  • May 12, 2011 at 2:23 pm

    #250885

    sql server is not using more than 3gb causing performace issues.

    total ram is 8gb

    windows 2003 32 bit

    sql 2005 sp3 32 bit

    awe enabled,lock pages enabled.

    sql using 3gb ram only.

    i want to sql to be use 6gb.

    any other setting do i need to change?any help?

  • May 12, 2011 at 6:01 pm

    #1324040

    1. Enable PAE (Physical Address Extension) at the OS level .

    2. Enable AWE and Set Max Memory = 6 GB

    3. Use Lock Pages in Memory

    Thank You,

    Best Regards,

    SQLBuddy

  • May 12, 2011 at 10:35 pm

    #1324080

    i did everything.any help?

  • May 12, 2011 at 11:23 pm

    #1324087

    What edition of SQL Server 2005 are you running and are you running on a physical or virtual server?

  • May 13, 2011 at 3:48 am

    #1324149

    you made the suggested changes as indicated by SQLBuddy and still experience the issue??

  • May 13, 2011 at 8:37 am

    #1324330

    i did all changes,sql2005Enterprise sp3

  • May 13, 2011 at 9:21 am

    #1324388

    Are you running Windows Standard or Enterprise Edition? If you are running Windows Standard Edition, you will not be able to access 6 GB of memory.

    From SQL Server 2005 Books Online:

    http://msdn.microsoft.com/en-us/library/ms190673(v=SQL.90).aspx"

    Enabling AWE Memory for SQL Server

    ...

    The physical memory accessible by AWE depends on which operating system you are using. The following list provides the maximum physical memory accessible by each Windows Server 2003 operating system at the time of writing.

    Windows Server 2003, Standard Edition supports physical memory up to 4 GB.

    Windows Server 2003, Enterprise Edition supports physical memory up to 32 GB.

    Windows Server 2003, Datacenter Edition supports physical memory up to 64 GB."

  • May 13, 2011 at 9:55 am

    #1324430

    select * from sys.dm_os_performance_counters

    where counter_name = 'Page life expectancy'

    provide value of this counter,RAM allocation is depend on the load of the server,this counter will tell you SQL Server required RAM or not

    Regards,
    Syed Jahanzaib Bin Hassan
    BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog
    www.aureus-salah.com

  • May 13, 2011 at 12:43 pm

    #1324514

    winfowd 2003r2 32 bit enterprise sp2

    sql2005 32bit enterprise sp3

    object _name cntr_value cntr_type

    buffermanager 732 65792

    buffer node 732 65792

  • May 13, 2011 at 1:13 pm

    #1324536

    Did you restart SQL Server after setting lock pages in memory?

    How large is the database actual space used in the data files?

  • May 13, 2011 at 7:00 pm

    #1324590

    i did restart

  • May 15, 2011 at 6:58 pm

    #1324835

    http://www.sqlservercentral.com/Forums/Topic1107587-360-1.aspx

    Regards,
    Shivrudra W

  • May 16, 2011 at 7:09 am

    #1325008

    We have covered the simple things that can be covered on a forum thread. I recommend you get a professional tuner to remote into your system and do a quick review to find out the source of your problem.

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

  • May 16, 2011 at 2:25 pm

    #1325470

    i did,around 300 GB

  • May 16, 2011 at 8:44 pm

    #1325561

    Is the problem resolved ? Could you provide us an update ?

    Thank You,

    Best Regards,

    SQLBuddy

Viewing 15 posts - 1 through 15 (of 19 total)

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