64 bit memory and what's free

  • I have a 64 bit box with 16774776 bytes ram (from task manager).

    In properties I have minimum set to 0, maximum set to 14000.

    I have a local account with lock pages in memory that runs the SQL Server service.

    Currently there are 537888 bytes free. I was expecting 1.5 or more gigs of RAM free...?

  • I am taking a guess you meant 16774776 KB which is (~16GB).

    So if you have 16GB, and you set SQL Server's max memory to 14,000MB (13.67GB); the rest of memory is for OS.

    Other applications running on your computer and the operating system also take up memory. So if the free memory is not 2.33GB; then check what other resources are taking up memory. Thanks.

    Mohit.

    [font="Arial"]---

    Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
    Microsoft FTE - SQL Server PFE

    * Some time its the search that counts, not the finding...
    * I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]

    How to ask for help .. Read Best Practices here[/url].

  • Yep, I have SQL memory set 0 minimum to 14000 maximum

    Yes, I had sorted by memory in task manager. The largest memory consumer was SQL with around 127 meg of RAM. I'll have to double check again.

    I have a dev box, except it's a quad core instead of eight with 16 gigs of RAM too. It has just under 1600 meg free. It did dip down to 500 overnight from midnight until 5 a.m. hmmm....

  • DBCC Memorystatus may help. It will at least show you how much AWE is currently being used. It's not unusual at all for the os to be using a gig or 2.

    Tim White

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


    DBCC Memorystatus may help. It will at least show you how much AWE is currently being used. It's not unusual at all for the os to be using a gig or 2.

    Because he is running a 64-bit box he does not need to use AWE; in 64-bit edition he can address the full memory. I guess question is you are running 64-bit version of OS/SQL Server correct?

    Thanks.

    Mohit.

    [font="Arial"]---

    Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
    Microsoft FTE - SQL Server PFE

    * Some time its the search that counts, not the finding...
    * I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]

    How to ask for help .. Read Best Practices here[/url].

  • ooops, my bad. Good call Mohit. Wasn't thinking 64-bit when I wrote.

    Tim White

  • Mohit (3/26/2009)


    2 Tim 3:16 (3/26/2009)


    DBCC Memorystatus may help. It will at least show you how much AWE is currently being used. It's not unusual at all for the os to be using a gig or 2.

    Because he is running a 64-bit box he does not need to use AWE; in 64-bit edition he can address the full memory. I guess question is you are running 64-bit version of OS/SQL Server correct?

    Thanks.

    Mohit.

    Yes it is 64 bit Windows 2003.

    I suspect there's ArcServe Agent that runs backups around midnight...seems like it's a memory hog.

  • Sorry I have never used ArcServe Agent, I like native SQL Server Backups more :).

    I did a quick search on google and it seems alot of people are complaining about ArcServe Agent and memory issues.

    Mohit.

    [font="Arial"]---

    Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
    Microsoft FTE - SQL Server PFE

    * Some time its the search that counts, not the finding...
    * I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]

    How to ask for help .. Read Best Practices here[/url].

  • the maximum memory "limit" only applies to some of MSSQL's use of memory. I have a server with 8GB memory and I'd set it to something like 6GB max but found it was using over 7GB. I ended up finding out that the maximum isn't a true maximum but only a max for certain parts of MSSQL's memory usage. So I set the max back down to around 5GB. I can't remember what parts are constrained by the Max value and what parts are not, but there are some memory structures that are not bound by the Max value.

    This may help if you find your sqlservr.exe process using more than you expected

Viewing 9 posts - 1 through 8 (of 8 total)

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