January 27, 2006 at 2:09 pm
Brand new install and no matter what I do I can't get SQL to use anything beyond 4GB of memory.
SQL 2005 Standard 64-bit edition - got this as a freebie from the recent MS launch event
Windows 2003 Server, x64 Enterprise edition
single AMD Opteron 280, dual-core x64
8GB RAM - all recognized by the OS
SELECT @@VERSION returns this:
Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
It's my understanding that in a 64-bit environment SQL should just naturally use as much memory as the OS has available. Initial load testing pushed memory usage in task manager up to 3.90GB and capped there. Even though it's in 64-bit mode I went ahead and set the "Lock pages in memory" policy to the SQL account and enabled AWE in SQL's memory settings. Testing showed that this made no difference and SQL was still capped at just under 4GB.
What am missing here? I've searched all over online and can't find anything to explain what I'm seeing. I'm open to any suggestions here and it's not in production yet so I can still easily make changes on the fly.
Thanks for any help you can offer me here!
- jc
January 30, 2006 at 8:00 am
This was removed by the editor as SPAM
January 30, 2006 at 9:05 am
Hey thanks for sticking up for me here The problem hasn't resolved itself in any fashion and we're getting closer to wanting to go live with the server - actually servers as we've got 2 that are replication partners, both with the same confusing 4GB memory limitation.
-jc
February 6, 2006 at 10:14 am
Any thoughts on this?
December 16, 2006 at 4:36 pm
Ancient thread, but the answer is in the event itself. You are running the 32-bit version of SQL.
Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply