April 3, 2009 at 9:41 am
EdVassie (4/3/2009)
Ed what fix are you refering to?
Apologies, I got my SQL versions mixed up. However, there are fixes for AWE issues post SP2, but nothing that is pervasive.
No need. We're all trying to help right. Just thought I'd missed a trick 🙂
April 9, 2009 at 11:14 am
Hi SA,
I have the similar issues on your posting questions.
I have Window 2003 Enterprise sp2 32-bit and SQL 2008 and my hardware configuration:
DELL Dual Socket Demps/Woodcrest/PowerEdge 1900/2900
Intel 2.0 GHx 1333FSB Harpertown \Xeon 5405 (Quad Core)
Hitachi \ 1000GB: SATA2: 72000RPM
Dell \9G Drive Controller.
C: RAID 1
D: RAID 10
E: RAID 1
Can you please share your server configuration on:
1. Boot.ini and SQL Server 2008.
Enclosed are my setup steps that I perform:
1.Edit Boot.ini file
[Boot Loader]
Timeout=30
Default=multi(0)disk(0)rdisk(0)partition(1) \WINDOWS
[Operating Systems]
Multi(0) disk(0) rdisk(0) partition(1) \WINDOWS=”Window Server 2003, Standard” /nonexcute=optout /fastdetect /3GB /userva=3030
2. Run T-SQL scripts
Use master
Go
EXECUTE sp_configure 'show advanced options', 1;
go
RECONFIGURE;
go
Exec sp_configure ‘AWE enabled’, 1
go
Reconfigure with override
go
Exec sp_configure ‘max server memory’, 6656
go
Reconfigure with override
go
3.Run secpol.msc
Thanks,
Edwin
April 9, 2009 at 11:28 am
I'm having this issue on Windows 2003 EE and SQL 2005 EE SP3
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect /PAE
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
C through F drives RAID 10
Have you tried to reboot after the /3GB and the secpol.msc but before making the change? Any messages in the SQL logs about AWE?
April 9, 2009 at 11:52 am
SA,
Many thanks for your help.
My boot.ini did not have the following line:
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
Should I add the above line and what for?
I did not see the AWE in the SQL Server 2008 log files.
C:\Program Files\Microsoft SQL Server\MSSQL10.ComputerName\MSSQL\Log
April 9, 2009 at 12:04 pm
Have you restarted SQL Server services?
After the restart, the most recent startup log should contain the words “Address Windowing Extensions enabled” early in the log.
April 9, 2009 at 12:12 pm
Yes, I found on the previous sql log. The SQL logs " Address Windowing Extensions (AWE) requires the 'lock page in memory' privilege which is not currently present in the access token of the process."
Then, I updated my boot.ini and run the gpedit.msc to add SQL Server startup account.
I will reboot the window server and sql server 2008 services. Will update you shortly.
Now, my sql server still run and create 250 GB database. 🙂
April 9, 2009 at 12:40 pm
SA,
The SQL logs indicated " Adderess Windowing Extension is enabled. This is an informational message only; no user action is required"
Did my 2003 Window and SQL 2008 ready to take the max utilize RAM?
Thanks,
Edwin
April 9, 2009 at 12:45 pm
Yes, your SQL instance has AWE enabled.
As another verification you could go in to Perfmon and look for the Total Server Memory and Target Server Memory counters under SQL Server: Memory object. It should show you the 6GB you have allocated.
April 9, 2009 at 1:34 pm
SA
The MEMORYCLERK_SQLBUFFERPOOL (Node 0)
VM Reserved 1594872KB
VM Commited 8064KB
AWE Allocated 262144KB
SM Reserved 0 KB
SM Commited 0 KB
SinglePage Allocator 0 KB
MultiPage Allocator 2096 KB
April 13, 2009 at 7:06 am
Reconfiguring AWE worked and SQL Server is feeling much better.
Thank you all for your help!!!
April 13, 2009 at 10:45 am
Excellent news!
April 13, 2009 at 12:16 pm
I think it had to do with the order in which I did this. For future reference -
1. Enabled PAE / 3GB which ever applicable or both (boot.ini)
2. Provide Lock pages in memory privilege via secpol.msc
3. Reboot
4. Configure AWE using sp_configure
5. Restart SQL Services
August 21, 2009 at 10:39 am
Finally an article that describes this in a detailed fashion... thanks to everyone for contributing.
However I still have some questions :S
My SQL server was using 1.7gb of memory in Task Manager before any changes...
I have tried the /3GB switch in the boot.INI without AWE, and it was going up to 2.8GB at one point (which I suspect is similar if not the same to the 3GB limit in the BOOT.INI)...
Now I have adjusted BOOT.INI to /PAE (removed the /3GB) and configured AWE, the result is that the sqlserver process is using 68mb in Task Manager, however, it seems to be using 1958200 using perfmon with the SQL counters.
Does this mean that this is only using 2gb of physical memory? (I do not see this memory available to anything else in the Task Manager)
Should I be using /PAE and /3GB together, as well as AWE, in order to better utilize the 4GB of physical RAM on the server?
Thanks,
Dominic
August 21, 2009 at 11:16 am
Just to Chime in here. I think my network staff had to modify the server's boot.ini file in order to put the finishing touch on increasing the memory available to SQL.
August 21, 2009 at 11:52 am
Chris (8/21/2009)
Just to Chime in here. I think my network staff had to modify the server's boot.ini file in order to put the finishing touch on increasing the memory available to SQL.
Has it been setup to /3GB and /PAE or just /3GB ?
Viewing 15 posts - 31 through 44 (of 44 total)
You must be logged in to reply to this topic. Login to reply