Post reply

Any draw backs to using Flag 836 with SQL Server 2008 r2 Ent?

  • April 13, 2011 at 9:12 am

    #389269

    Any draw backs to using Flag 836 with SQL Server 2008 r2 Ent?

  • April 13, 2011 at 9:46 am

    #1311118

    http://support.microsoft.com/kb/920093 (4/13/2011)

    Trace flag 836: Use the max server memory option for the buffer pool

    Trace flag 836 causes SQL Server to size the buffer pool at startup based on the value of the max server memory option instead of based on the total physical memory. You can use trace flag 836 to reduce the number of buffer descriptors that are allocated at startup in 32-bit Address Windowing Extensions (AWE) mode.

    Trace flag 836 applies only to 32-bit versions of SQL Server that have the AWE allocation enabled. You can turn on trace flag 836 only at startup.

    i had to look that one up Richard;

    nowadays, I'd expect your 2008R2 server to be 64 bit right? so in that case it wouldn't apply, as it's only for 32 Bit systems; beyond that, I'll wait for other experts to weigh in for ramifications on a 32 bit architecture.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • April 13, 2011 at 9:50 am

    #1311127

    Let's turn the question around. Why do you want to use it?

    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

  • April 13, 2011 at 12:33 pm

    #1311249

    I have the max memory set to 66 Gigs and the min memory set to 16 Gigs. The server is a 70 Gigs box, but until recently SQL was not using the 66 Gigs. I have discovered the 836 Flag is ignored on 64 bit. The server is now using all the 66 GB memory. It took it 4 hours to creep up the memory usage. Thanks

  • April 13, 2011 at 12:34 pm

    #1311251

    Yes its 64 bit so the flag will be ignored. Thanks

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

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