Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Server Administration


Server Administration

Author
Message
bvbellomo
bvbellomo
Old Hand
Old Hand (341 reputation)Old Hand (341 reputation)Old Hand (341 reputation)Old Hand (341 reputation)Old Hand (341 reputation)Old Hand (341 reputation)Old Hand (341 reputation)Old Hand (341 reputation)

Group: General Forum Members
Points: 341 Visits: 2079
I was correct, but did not like this question. None of the options do anything, so they are all equivalent.
Alex Rosa
Alex Rosa
SSC Rookie
SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)SSC Rookie (46 reputation)

Group: General Forum Members
Points: 46 Visits: 933
actually this was a trick for who don't how 64bit env works.

the first 2 options are valid in 32bit env, and I bet that a lot of people will choice AWE settings :-D

---------------------
Alex Rosa
http://www.keep-learning.com/blog
Swarndeep
Swarndeep
SSC-Addicted
SSC-Addicted (483 reputation)SSC-Addicted (483 reputation)SSC-Addicted (483 reputation)SSC-Addicted (483 reputation)SSC-Addicted (483 reputation)SSC-Addicted (483 reputation)SSC-Addicted (483 reputation)SSC-Addicted (483 reputation)

Group: General Forum Members
Points: 483 Visits: 361
Thanks for all of your comments.

Setting Maximum Memory Parameter is also a good option and nothing against this. However, I personally experienced that Maximum Memory Parameter is most useful when lock pages option has been enabled from Windows.

Thanks

Swarndeep

http://talksql.blogspot.com
Robert Frasca
Robert Frasca
SSChasing Mays
SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)

Group: General Forum Members
Points: 608 Visits: 740
The answer is incorrect. AWE can be used in 64-bit and some people recommend that it should be set because it helps SQL Server manage memory by not allowing the working set to be trimmed. (Note: lock pages in memory must also be set.) This blog entry explains it pretty well.

http://blogs.msdn.com/psssql/archive/2007/10/18/do-i-have-to-assign-the-lock-privilege-for-local-system.aspx

"Beliefs" get in the way of learning.
Cliff Jones
Cliff Jones
SSCarpal Tunnel
SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)

Group: General Forum Members
Points: 4069 Visits: 3648
Robert Frasca (1/11/2010)
The answer is incorrect. AWE can be used in 64-bit and some people recommend that it should be set because it helps SQL Server manage memory by not allowing the working set to be trimmed. (Note: lock pages in memory must also be set.) This blog entry explains it pretty well.

http://blogs.msdn.com/psssql/archive/2007/10/18/do-i-have-to-assign-the-lock-privilege-for-local-system.aspx


I agree with the Lock Pages in memory, not what the question asked, but the article clearly suggests that:

This is why for 64bit systems, you don't need to set the 'awe enabled' option to 1 (it is actually ignored on 64bit systems).
Robert Frasca
Robert Frasca
SSChasing Mays
SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)

Group: General Forum Members
Points: 608 Visits: 740
Did you read the blog post from the CSS SQL Server group engineers? The AWE switch is NOT ignored and it is recommended as a best practice. Here is a snippet from the blog post:

So, the purpose of AWE for 32bit systems was to access more memory. But for 64bit, AWE APIs are used to avoid a working set trim. So SQL Server will automatically use the AWE APIs provided the 'lock pages in memory' privilege is set (and your are using Enterprise Edition). If you want to read more about the AWE APIs, look here in MSDN: http://msdn2.microsoft.com/en-us/library/aa366527.aspx



"Beliefs" get in the way of learning.
Cliff Jones
Cliff Jones
SSCarpal Tunnel
SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)

Group: General Forum Members
Points: 4069 Visits: 3648
Yes I did. Apparently I do not interpret it the same way that you do. I took the following to mean that you did not need to enable AWE to use the AWE API's on 64 Bit. We do not do this with our 64 bit servers. We were able to prevent the working set from being trimmed by merely locking pages in memory (in addition to setting Min/Max Memory properly).


For 64bit systems, the virtual address space limitation is not an issue. However, if an application wants to "lock its memory" or avoid its working set from being trimmed, then it can achieve this by using the AWE APIs. Again, in order to use these APIs, you must have the 'lock pages in memory' privilege set. This is why for 64bit systems, you don't need to set the 'awe enabled' option to 1 (it is actually ignored on 64bit systems).
Tom Garth
Tom Garth
Ten Centuries
Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)Ten Centuries (1K reputation)

Group: General Forum Members
Points: 1013 Visits: 1499
I never gave a thought to 64 bit Windows/SQL Servers having different built in memory allocation settings than the 32 bit versions.

In fact, I figured that Windows Server 2008 wouldn't need an adjustment in 64 or 32, but I've olny dealt with the 64 bit version so far.

Thanks for the question.

Tom Garth
Vertical Solutions

"There are three kinds of men. The one that learns by reading. The few who learn by observation. The rest of them have to pee on the electric fence for themselves." -- Will Rogers

Robert Frasca
Robert Frasca
SSChasing Mays
SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)SSChasing Mays (608 reputation)

Group: General Forum Members
Points: 608 Visits: 740
Cliff Jones (1/11/2010)

Again, in order to use these APIs, you must have the 'lock pages in memory' privilege set. This is why for 64bit systems, you don't need to set the 'awe enabled' option to 1 (it is actually ignored on 64bit systems).



Perhaps we're having a semantic argument. There are a number of articles around that explain how 64-bit memory management works with the AWE Enabled option set. In fact, if you've turned on 'lock pages in memory' I believe you'll find that the AWE Enabled box is checked whether you like it or not; however, if you don't have "lock pages in memory" set then you can't set the AWE enabled switch. The overriding point is that AWE functionality is used on 64-bit machines. It isn't just a 32-bit feature. The difference is that the functionality provides a different set of benefits in a 64-bit environment.

"Beliefs" get in the way of learning.
Cliff Jones
Cliff Jones
SSCarpal Tunnel
SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)

Group: General Forum Members
Points: 4069 Visits: 3648
Robert Frasca (1/11/2010)
Cliff Jones (1/11/2010)

Again, in order to use these APIs, you must have the 'lock pages in memory' privilege set. This is why for 64bit systems, you don't need to set the 'awe enabled' option to 1 (it is actually ignored on 64bit systems).



Perhaps we're having a semantic argument. There are a number of articles around that explain how 64-bit memory management works with the AWE Enabled option set. In fact, if you've turned on 'lock pages in memory' I believe you'll find that the AWE Enabled box is checked whether you like it or not; however, if you don't have "lock pages in memory" set then you can't set the AWE enabled switch. The overriding point is that AWE functionality is used on 64-bit machines. It isn't just a 32-bit feature. The difference is that the functionality provides a different set of benefits in a 64-bit environment.


I was not aware of that, point taken. I agree the question was lacking. I think what people should take away from this is that you want to get the memory settings on 64 bit correct; set Min/Max memory, and lock pages in memory. If the working set gets trimmed, performance is in the toilet.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search