SQL server not taking assigned memory

  • Hello All,

    I have a SQL server which has 16 GB of RAM. Recently we had some issue with the Physical memory so we replaced the faulty memory. Since then My SQL server is not taking the assigned memory. I assigned max memory 13 Gb\ and Min 12 GB, but when I checked I can only see that the SQL server is only utilizing 139 MB of Memory.

    Any suggesstion regarding this would be appreciated.

    Thanks in Advance.

  • Ziljan4 (3/9/2009)


    Hello All,

    I have a SQL server which has 16 GB of RAM. Recently we had some issue with the Physical memory so we replaced the faulty memory. Since then My SQL server is not taking the assigned memory. I assigned max memory 13 Gb\ and Min 12 GB, but when I checked I can only see that the SQL server is only utilizing 139 MB of Memory.

    Any suggesstion regarding this would be appreciated.

    Thanks in Advance.

    Hi,

    maybe in 32 bit version you have to enable AWE flag in the Server Property->Memory.

    Mauro

  • You might want to check that the OS sees the RAM first. If it wasn't properly inserted or if the new RAM is bad too, that could cause a problem.

    Also, I wouldn't assign a mimimum memory in SQL. Leave that as zero so SQL isn't hogging the memory when it doesn't need it.

    If the OS sees the new RAM, have you tried restarting the SQL Services? SQL Server 2005 doesn't do hot-swap RAM so far as I know. Your problem might be that you tried a hot-swap on a box that OSwise can deal with it but SQLwise can't.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Thanks Mauro and Brandie for your comments. The server is 64 bit and the OS is recognizing the memory. It showing what the system has.

    Thanks again.

  • Did any of our comments help? Is your problem resolved?

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • Did you set the intial RAM size in SQL to at least 10240MB (10GB)?

    Are you just looking from "Task Manager"? If so, it will not show the eunning instance of SQL using the RAM. Use a third party app like Idera to see the ram utilization.

    I made that mistake once before. Then I used our Idera app ind it reported correctly. Why you ask? Because eventhough you are running 64bit, you are still "Paging" the memory and it will not show it. There's only one version that will and it's the Itanium version.

    You might also wnat to make sure that "AWE" is sekected also, just in case. Theoretically it is not required to have the /PAE for the boot ini.

  • PerfMon can also be used to check things like RAM usage, even for SQL Server. I can't remember which SQL Server counter it is, though, off the top of my head. Should be listed in BOL.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • /*

    http://blogs.solidq.com/EN/rdyess/Lists/Categories/Category.aspx?Name=Memory

    I noticed that I could quite a bit of basic memory information from the system

    information, so I thought I would show you a very basic query you could use for

    your own systems. This query attempts to show some of the basic memory areas

    in a SQL Server 2005 or 2008 installation.

    */

    --Memory columns of sys.dm_os_sys_info

    SELECT

    --Amount of physical memory on server

    physical_memory_in_bytes

    , physical_memory_in_bytes / 1024 / 1024.00 as physical_memory_in_MB

    ,virtual_memory_in_bytes

    , virtual_memory_in_bytes / 1024 / 1024.00 as virtual_memory_in_MB

    --Committed physical memory in buffer pool

    --Does not include MemToLeave memory area

    ,bpool_committed AS 'Number of 8KB buffers in buffer pool'

    , bpool_committed * 8 / 1024.00 as bpool_committed_in_MB

    , bpool_commit_target AS 'Number of 8KB buffers needed by the buffer pool'

    , bpool_commit_target * 8 / 1024.00 as bpool_commit_target_in_MB

    ,CASE

    WHEN bpool_commit_target > bpool_committed THEN 'Extra memory needed from OS for Buffer Pool'

    WHEN bpool_commit_target < bpool_committed THEN 'Memory may be released from Buffer Pool to OS'

    END AS 'Status of Dynamic Memory'

    , bpool_visible AS 'Number of 8KB Buffers in Buffer Pool that are directly accessible in the processes VAS.'

    , bpool_visible * 8 / 1024.00 as bpool_directly_accessible_VAS_in_MB

    FROM sys.dm_os_sys_info

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • DBCC MEMORYSTATUS will show awe used.

    Tim White

  • even for 64-bit, you still need to "lock pages in memory"

    Open the Group Policies Console:

    START-RUN , enter - gpedit.msc

    Computer Configuration - Windows Settings - Security Settings –

    -Local Policies - User Rights Assignment

    In the detail, open “Lock Pages In Memory”.

    Click – ADD

    Add the SQL Server start-up acct.

    Tim White

  • ...and then of course remember to restart the SQL services.....

    _______________________________________________________________________
    For better assistance in answering your questions, click here[/url]

  • 2 Tim 3:16 (3/10/2009)


    even for 64-bit, you still need to "lock pages in memory"

    Open the Group Policies Console:

    START-RUN , enter - gpedit.msc

    Computer Configuration - Windows Settings - Security Settings –

    -Local Policies - User Rights Assignment

    In the detail, open “Lock Pages In Memory”.

    Click – ADD

    Add the SQL Server start-up acct.

    This off course only if you want sqlserver to be able to keep its allocated memory !

    This is service account based, so don't use that service account to perform everything on that server!

    There are a couple of nice articles that give some advice and caution regarding the usage of "lock pages in memory".

    They are realy worth reading !!

    Start with this one:

    http://blogs.technet.com/askperf/archive/2008/03/25/lock-pages-in-memory-do-you-really-need-it.aspx

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

Viewing 12 posts - 1 through 11 (of 11 total)

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