Comments on: Sql Server 2005 AWE on Windows 2003 32-bit http://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/ 季庄新闻--Haidong Ji's Blog Wed, 04 Jan 2012 09:32:09 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: Haidong Jihttp://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/comment-page-1/#comment-17954 Haidong Ji Sat, 03 Jul 2010 02:42:07 +0000 http://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/#comment-17954 Hi Ruben, At this point I am not doing much SQL Server work, so my skills are a bit rusty. And I don't want to lead you down the wrong path. I'd suggest you ask the same question at Stackoverflow or Microsoft's forum. You probably can get better answers there. Good luck! Hi Ruben,

At this point I am not doing much SQL Server work, so my skills are a bit rusty. And I don’t want to lead you down the wrong path.

I’d suggest you ask the same question at Stackoverflow or Microsoft’s forum. You probably can get better answers there.

Good luck!

]]> By: Rubenhttp://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/comment-page-1/#comment-17953 Ruben Fri, 02 Jul 2010 13:48:48 +0000 http://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/#comment-17953 Hi I read all post but still without understand completely. Scenario: Windows 2003 Enterprise 64 bits SQL Server 2005 Standard 64 bits AWE enabled 8 GB RAM min memory: 6 GB max memory: 6 GB boot.ini, not modified Lock pages in memory: local service, network, system SQL Server (MSSQLSERVER) Log on as: local system account -- in services mmc -- Task Manager, PF of 1,8 GB, but RAM available is more than 6, GB. So I understand that SQL SERVER is not taking all memory that it could take. It's possible with this paremeters be able to SQL SERVER spend more memory? Do I have forgotten something? Physical memory, 6 GB available, god, i could not see task manager, its killing me! Thanks , excellent post! Hi

I read all post but still without understand completely.

Scenario:

Windows 2003 Enterprise 64 bits
SQL Server 2005 Standard 64 bits
AWE enabled
8 GB RAM
min memory: 6 GB
max memory: 6 GB
boot.ini, not modified
Lock pages in memory: local service, network, system
SQL Server (MSSQLSERVER) Log on as: local system account — in services mmc –

Task Manager, PF of 1,8 GB, but RAM available is more than 6, GB. So I understand that SQL SERVER is not taking all memory that it could take.

It’s possible with this paremeters be able to SQL SERVER spend more memory? Do I have forgotten something?

Physical memory, 6 GB available, god, i could not see task manager, its killing me!

Thanks , excellent post!

]]> By: sunnyhttp://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/comment-page-1/#comment-17920 sunny Thu, 20 May 2010 14:34:11 +0000 http://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/#comment-17920 Hello Haidong Explain in detailed about awe i am in confusion? How its work? Hello Haidong

Explain in detailed about awe i am in confusion?

How its work?

]]> By: sunnyhttp://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/comment-page-1/#comment-17919 sunny Thu, 20 May 2010 14:30:56 +0000 http://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/#comment-17919 hello Haidong, I am asking simple Q? why the awe is enabling and is it only for 32-bit. How to give the space to the large amounts the awe provide? If awe enabled, is it their any performance issues? hello Haidong,

I am asking simple Q?

why the awe is enabling and is it only for 32-bit.

How to give the space to the large amounts the awe provide?

If awe enabled, is it their any performance issues?

]]> By: Haidong Jihttp://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/comment-page-1/#comment-17764 Haidong Ji Tue, 08 Sep 2009 15:49:38 +0000 http://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/#comment-17764 Hi Rich, Yes, SQL Server engine will be able to use more than 2GB/3GB of RAM, if 1. AWE is enabled, and 2. Lock pages in memory is enabled for the startup account. You can verify this by looking at: select bpool_visible from sys.dm_os_sys_info In Sandeep's case, it sounded like AWE was enabled, but lock page in memory was not. Hope this helps and good luck! Hi Rich,

Yes, SQL Server engine will be able to use more than 2GB/3GB of RAM, if

1. AWE is enabled, and
2. Lock pages in memory is enabled for the startup account.

You can verify this by looking at:

select
bpool_visible
from
sys.dm_os_sys_info

In Sandeep’s case, it sounded like AWE was enabled, but lock page in memory was not.

Hope this helps and good luck!

]]> By: Richhttp://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/comment-page-1/#comment-17763 Rich Sat, 05 Sep 2009 14:36:31 +0000 http://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/#comment-17763 I'm interested in a more thorough answer to Sandeep's question as we are running the same setup; SQL Server 2005 Enterprise 32-bit on Windows Server 2003 Enterprise R2 SP2 64-bit with 32GB Physical RAM and we CANNOT use 64-bit SQL. We HAVE to use 32-bit SQL because we use an OLEDB driver that is only 32-bit, no 64-bit available. Question1. Given the provided setup above, if AWE is enabled, will the process actually use more than 2GB/3GB of RAM? Question2. If the answer to question 1 is yes, then how can I verify this? What specific PerMon counter will clearly display this? Thanks! I’m interested in a more thorough answer to Sandeep’s question as we are running the same setup; SQL Server 2005 Enterprise 32-bit on Windows Server 2003 Enterprise R2 SP2 64-bit with 32GB Physical RAM and we CANNOT use 64-bit SQL.
We HAVE to use 32-bit SQL because we use an OLEDB driver that is only 32-bit, no 64-bit available.

Question1. Given the provided setup above, if AWE is enabled, will the process actually use more than 2GB/3GB of RAM?

Question2. If the answer to question 1 is yes, then how can I verify this?
What specific PerMon counter will clearly display this?
Thanks!

]]> By: Haidong Jihttp://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/comment-page-1/#comment-17747 Haidong Ji Tue, 30 Jun 2009 01:19:45 +0000 http://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/#comment-17747 Sandeep, In this case, I would put in 64-bit edition of Sql Server. Sandeep,

In this case, I would put in 64-bit edition of Sql Server.

]]> By: Sandeephttp://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/comment-page-1/#comment-17746 Sandeep Thu, 25 Jun 2009 22:22:06 +0000 http://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/#comment-17746 HI MJ, We have SQL Server Standard edition(32 BIt) Installed on Windows 2003 R2 (64BIt) OS. This server has 16Gb RAM but my sql server db is not taking more than 3.6GB. DBCC MEMORYSTATUS showing VM Reserved 3652068 VM Committed 3651220 AWE Allocated 0 Reserved Memory 1024 Reserved Memory In Use 0 I can use upto 12 GB memory for SQL server. Is it possible to assign ? If yes HOw? HI MJ,
We have
SQL Server Standard edition(32 BIt) Installed on Windows 2003 R2 (64BIt) OS. This server has 16Gb RAM but my sql server db is not taking more than 3.6GB.
DBCC MEMORYSTATUS showing
VM Reserved 3652068
VM Committed 3651220
AWE Allocated 0
Reserved Memory 1024
Reserved Memory In Use 0

I can use upto 12 GB memory for SQL server. Is it possible to assign ? If yes HOw?

]]> By: Haidong Jihttp://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/comment-page-1/#comment-17312 Haidong Ji Fri, 19 Sep 2008 16:57:44 +0000 http://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/#comment-17312 Hi MJ, For 64-bit systems, PAE is not supported so no need to put that into boot.ini. http://www.microsoft.com/whdc/system/platform/server/PAE/PAEdrv.mspx Slava Ok wrote a post a few years to address AWE and 64-bit here. I don't fully understand, but I trust he knows what he's talking about :) http://blogs.msdn.com/slavao/archive/2005/04/29/413425.aspx Hope this helps. Hi MJ,

For 64-bit systems, PAE is not supported so no need to put that into boot.ini.

http://www.microsoft.com/whdc/system/platform/server/PAE/PAEdrv.mspx

Slava Ok wrote a post a few years to address AWE and 64-bit here. I don’t fully understand, but I trust he knows what he’s talking about :)

http://blogs.msdn.com/slavao/archive/2005/04/29/413425.aspx

Hope this helps.

]]> By: MJhttp://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/comment-page-1/#comment-17311 MJ Fri, 19 Sep 2008 16:09:52 +0000 http://www.haidongji.com/2007/09/06/sql-server-2005-awe-on-windows-2003-32-bit/#comment-17311 Hi, you answered a question for someone, the same question I wanted to ask but could you please provide an explanation for why you would want to set the /PAE and AWE on a x64 Windows Server 2003 Enterprise and a SQL 2005 Server Enterprise? I could really use the help! thank you Question: Do we need to configure Sql Server 2005 to use AWE on 64-bit Windows 2003? Thanks. Answer: Yes, AWE should be turned on, even for 64-bit systems. Unfortunately, Lock Page in Memory only works for Sql Server 2005 Enterprise Edition. Hi, you answered a question for someone, the same question I wanted to ask but could you please provide an explanation for why you would want to set the /PAE and AWE on a x64 Windows Server 2003 Enterprise and a SQL 2005 Server Enterprise? I could really use the help! thank you

Question: Do we need to configure Sql Server 2005 to use AWE on 64-bit Windows 2003? Thanks.
Answer: Yes, AWE should be turned on, even for 64-bit systems.
Unfortunately, Lock Page in Memory only works for Sql Server 2005 Enterprise Edition.

]]>