SQL Server 2008R2 Memory

  • Good Day.

    We are running an SQL Server 2008R2 ent 64 Bit on a server with 200 gig of memory . At the beginning of the week SQL Server only uses 50 gigs of memory. By Wednes it uses 150 gig and remains there . No memory is ever released . Should we lock down the memory ?

    Regards.

    Lian

  • lianvh 89542 (4/8/2013)


    At the beginning of the week SQL Server only uses 50 gigs of memory. By Wednes it uses 150 gig and remains there.

    SQL Server will consume memory based on the memory configuration in server properties. Default max value is 2000PB+ so if you've had some resource intensive stuff happening during the week, SQL will use up the whole lot!

    No memory is ever released . Should we lock down the memory ?

    Depends, is there anything else running on the box? If not then you can give the OS say 4-6GB memory and leave the rest to SQL Server.

    Why do you want to release the memory back to the OS?

    ---------------------------------------------------------

    It takes a minimal capacity for rational thought to see that the corporate 'free press' is a structurally irrational and biased, and extremely violent, system of elite propaganda.
    David Edwards - Media lens[/url]

    Society has varying and conflicting interests; what is called objectivity is the disguise of one of these interests - that of neutrality. But neutrality is a fiction in an unneutral world. There are victims, there are executioners, and there are bystanders... and the 'objectivity' of the bystander calls for inaction while other heads fall.
    Howard Zinn

  • SQL won't release memory unless the OS requests that it does (OS under memory pressure). It is always a good idea to set max server memory. As for what you set it to, that's complex. 🙂

    Take a read through chapter 4 of http://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/, it covers memory in detail.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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