Removing AWE memory allocation from a Windows 2008 Server

Heyas,

I have a 64-bit Windows Server server running just SQL server that has been experiencing some memory issues of late. Looking into this today I find that 8GB of 16 GB is allocated to just the AWE pool which I 64-bit SQL server can't utilize. How to remove this AWE allocation from the Windows Server pool.

Any assistance is welcome thank you.
AWE-Allocation.PNG
ZackGeneral IT Goto GuyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

yo_beeDirector of Information TechnologyCommented:
ZackGeneral IT Goto GuyAuthor Commented:
Hi Yo_bee

Different server and different question, my question on that post how to eliminate AWE entirely on the Windows Server memory allocation as it is not required for a 64-bit server as I understand it.

Thank you.
yo_beeDirector of Information TechnologyCommented:
Uncheck the setting under memory "Use AWE to allocate memory".  
This may introduce performance of your server and probably needs more memory in the long run.
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

yo_beeDirector of Information TechnologyCommented:
What does the native Task Manager show?
ZackGeneral IT Goto GuyAuthor Commented:
Hi Yo-Bee,

The AWE memory is already unchecked in SQL Server, my query is how can I remove this allocation entirely in Windows Server as Ramnmap shows it's consuming a fair bit.

Thank you.
yo_beeDirector of Information TechnologyCommented:
Can you show a list all your servers and memory being used?
Did you restart the SQLSERVER service?

You can also try this SQL statement to see what is being used by the SQL server.

SELECT 
  physical_memory_in_use_kb/1024 AS sql_physical_memory_in_use_MB, 
    large_page_allocations_kb/1024 AS sql_large_page_allocations_MB, 
    locked_page_allocations_kb/1024 AS sql_locked_page_allocations_MB,
    virtual_address_space_reserved_kb/1024 AS sql_VAS_reserved_MB, 
    virtual_address_space_committed_kb/1024 AS sql_VAS_committed_MB, 
    virtual_address_space_available_kb/1024 AS sql_VAS_available_MB,
    page_fault_count AS sql_page_fault_count,
    memory_utilization_percentage AS sql_memory_utilization_percentage, 
    process_physical_memory_low AS sql_process_physical_memory_low, 
    process_virtual_memory_low AS sql_process_virtual_memory_low
FROM sys.dm_os_process_memory; 

Open in new window

ZackGeneral IT Goto GuyAuthor Commented:
Hi Yo_bee,

Attached.

Thank you.
Results.xlsx
yo_beeDirector of Information TechnologyCommented:
Did you restart the SQLSERVER service?. That was not answered in your last reply?

I just ran RAMMAP on my SQL server and saw AWE.  I was not aware what that was until I just looked it up. https://msdn.microsoft.com/en-us/library/windows/desktop/aa366527(v=vs.85).aspx 

So something else maybe using AWE. Could be the SQLREPORTER or SQLAGENT
yo_beeDirector of Information TechnologyCommented:
Did you restart the SQLSERVER service?. That was not answered in your last reply?

I just ran RAMMAP on my SQL server and saw AWE.  I was not aware what that was until I just looked it up. https://msdn.microsoft.com/en-us/library/windows/desktop/aa366527(v=vs.85).aspx  

So something else maybe using AWE. Could be the SQLREPORTER or SQLAGENT
ZackGeneral IT Goto GuyAuthor Commented:
Hi yo-bee,

Sorry for the delay had to fix a network issue, I haven't restarted the SQL server on this server as of yet and can't until tonight.

I will check  SQLREPORTER or SQLAGENT and see if they are using AWE.

Thank you.
yo_beeDirector of Information TechnologyCommented:
If you made that change and the SQLSERVER service has not been restarted that might be the reason you are not seeing this change yet.
ZackGeneral IT Goto GuyAuthor Commented:
Hi Yo_bee,

I checked this is unlikely as the last reboot was 3 weeks ago and the other DBA has been overseas. I will restart and review though.

Thank you.
ZackGeneral IT Goto GuyAuthor Commented:
Hi Yo_bee,

Rebooted no difference in AWE allocation.

Thank you.
yo_beeDirector of Information TechnologyCommented:
You need to look at your process that are running and sum them up.

If you run a Powershell command

Get-Process |Export-Csv -Path .\Process.csv -NoTypeInformation 

Open in new window

This will give you some really good detail

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
EugeneZ ZhitomirskySQL SERVER EXPERTCommented:
check and try to "adjust"
 Lock Pages in Memory for the SQL Server Service Account,

--

not sure what your OS version ( 2008 or 2008R2).
in any case make sure to install the latest OS patches \SP


same for Sql server

---

just in case "Locking pages in memory may boost performance when paging memory to disk is expected. " https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-the-lock-pages-in-memory-option-windows
ZackGeneral IT Goto GuyAuthor Commented:
Hi Yo_Bee,

Cheers for the PowerShell suggestion. Found the process it was DTEXEC.exe which an SSIS component of SQL server. Further research revealed that some of the SSIS packages were executing in 32-bit mode which was causing the blowout in the memory when they ran according to Procmon.  Now forwarded the issue to the vendor dev team.

Cheers for the suggestion Eugene already checked that Locked page's settings before I posted.
EugeneZ ZhitomirskySQL SERVER EXPERTCommented:
I'm not sure if you are on the right track:  what did you see in the PS output that made DTEXEC your"target"?


did you check if you have patched OS\SQL server ( it can help if you can post details  -- try  select @@version)

--

see Solution
by:David Johnson

2008 server RAM usage is going to 97% however Task Manager is not showing anything.
https://www.experts-exchange.com/questions/28464113/2008-server-RAM-usage-is-going-to-97-however-Task-Manager-is-not-showing-anything.html
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.