<p>I've noticed that SQL Server 2005 x64 does not seem to lock pages into memory the same way SQL Server 2000 did.  In 2000 I could easily see from task manager that SQL had locked 8GB of ram with AWE.  I'm fairly certain I've got 2005 setup in an equivalent way.</p>

<p>Is this a normal x64 difference or am I forgetting a crucial setup option?</p>

[{'answer_id': 52665, 'author': 'Matt Rogish', 'author_id': 2590, 'author_profile': 'https://Stackoverflow.com/users/2590', 'pm_score': 2, 'selected': False, 'text': '<p>SQL Server 2005 x64 certainly doesn\'t need, or use, AWE; AWE is only to allow it to use > 4GB on 32 bit systems.</p>\n\n<p>You <em>can</em> use the old lock-pages-in-memory trick, but as this KB shows (<a href="http://support.microsoft.com/kb/918483" rel="nofollow noreferrer">http://support.microsoft.com/kb/918483</a>): "Note For 64-bit editions of SQL Server 2005, only SQL Server 2005 Enterprise Edition can use the Lock pages in memory user right."</p>\n'}, {'answer_id': 215792, 'author': 'Brent Ozar', 'author_id': 26837, 'author_profile': 'https://Stackoverflow.com/users/26837', 'pm_score': 1, 'selected': False, 'text': '<p>I\'ve seen permissions problems crop up a lot too - if the account you\'re using for the SQL Server service doesn\'t have the right permissions, it can\'t lock pages in memory even if you\'re running Enterprise Edition.  This blog entry by the PSS SQL Server Engineers is really helpful:</p>\n\n<p><a href="http://blogs.msdn.com/psssql/archive/2007/10/18/do-i-have-to-assign-the-lock-privilege-for-local-system.aspx" rel="nofollow noreferrer">PSS Engineers: Do I have to assign the Lock Pages in Memory privilege for Local System?</a></p>\n'}]
['https://Stackoverflow.com/questions/52169', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/-1/']