AWE on SQL SERVER 2012 and Windows Server 2008 Data Center?

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2012 » SQL 2012 - General » AWE on SQL SERVER 2012 and Windows Server...

AWE on SQL SERVER 2012 and Windows Server 2008 Data Center?

Rate Topic

Display Mode

Topic Options

Author

Message

Rogman

Posted Wednesday, March 20, 2013 9:58 AM

SSC Rookie

Group: General Forum Members
Last Login: Friday, June 07, 2013 6:15 PM
Points: 35, Visits: 200

We have SQL Server 2012 Enterprise 64-bit installed on a Windows Server 2008 Data Center 64-bit. For some reason AWE is allocating all the unused memory from the OS. It's my understanding that AWE was depricated from 2012, which would make sense since I can't find anywhere to disable it in the SQL config. Is there some other way that AWE would be installed and enabled? Some other applicaion? 2008 is not installed and this is a fresh install with 2012, not an upgrade.

Any thought you have would be appreciated.

Thanks.

Post #1433325

HowardW

Posted Wednesday, March 20, 2013 10:34 AM

Ten Centuries

Group: General Forum Members
Last Login: Today @ 3:06 AM
Points: 1,089, Visits: 7,919

How are you viewing that AWE is being used rather than regular memory allocation?

Post #1433338

Rogman

Posted Wednesday, March 20, 2013 12:15 PM

SSC Rookie

Group: General Forum Members
Last Login: Friday, June 07, 2013 6:15 PM
Points: 35, Visits: 200

I ran RamMap and it shows AWE using the amount of memory that I have specificed in SQL Server for the max memory setting (60GB). We allocated an additional 32GB (total of 96GB) to the server last night and the AWE allocation didn't increase when we did that so it apears to be using the Sql Server max memory configuration setting.

Post #1433398

opc.three

Posted Wednesday, March 20, 2013 10:30 PM

SSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 1:24 PM
Points: 6,826, Visits: 11,950

64-bit SQL Server still uses the AWE APIs to allocate memory in Windows. No need to worry there. Just set 'max server memory' properly and off you go.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato

Believe you can and you're halfway there. --Theodore Roosevelt

Everything Should Be Made as Simple as Possible, But Not Simpler --Albert Einstein

The significant problems we face cannot be solved at the same level of thinking we were at when we created them. --Albert Einstein

1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples. --Giordy

Post #1433581

GilaMonster

Posted Thursday, March 21, 2013 3:48 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 3:25 AM
Points: 38,073, Visits: 30,366

Don't mix up the AWE memory allocation API, which is used any time that locked pages is enabled, and the AWE setting which is only for 32 bit SQL.

Yes, if you have locked pages enabled you will see that the memory is allocated using the AllocPhysicalPages API call rather than the VirtualAlloc, that's how locked pages work, pages allocated via AllocPhysicaPages can't be paged out by the OS.

Set max server memory to a sensible value and you're fine.

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1433677

Rogman

Posted Thursday, March 21, 2013 10:13 AM

SSC Rookie

Group: General Forum Members
Last Login: Friday, June 07, 2013 6:15 PM
Points: 35, Visits: 200

Thanks for the replies! I finally found that this morning after poking around at some things. Just misleading that it shows AWE (which i interpreted as 32-bit) for locking the memory pages.

You guys are great as always.

Post #1433891

GilaMonster

Posted Thursday, March 21, 2013 11:56 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 3:25 AM
Points: 38,073, Visits: 30,366

The thing is, the memory allocated by AllocPhysicalPages is known as AWE memory, so it's not a misleading display, it's correct. AWE does not just mean the 32 bit memory extensions only.

In fact, other way around, the 32 bit memory extensions (to use memory above 4GB) use the AWE memory allocation APIs

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
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

Post #1433947

« Prev Topic | Next Topic »

Permissions