April 17, 2013 at 2:04 pm
Am a junior DBA and We have an issue from last couple of days. We have a server of Windows 2003 Standard Edtion of x64 bit with SP2. SQL Server is of 32bit running. Physical Memory on the server is 0f 4GB and SQL now running out of memory. Can we enable the AWE on a 64 bit OS machine where SQL is of 32 bit
Please suggest me
April 17, 2013 at 2:24 pm
you can but its of minimal use to you with a physical limitation of 4GB on the server.
what makes you think you are running out of memory?
How much memory is SQL using currently and have you enabled the /3GB switch in the boot.ini file?
---------------------------------------------------------------------
April 17, 2013 at 2:47 pm
With only 4 GB, I'd recommend adding the /3GB flag to boot.ini, not /PAE and not enabling AWE. When/if you add more memory to go over 4GB, then AWE is useful
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 17, 2013 at 3:30 pm
Is reboot of the server required after adding /3gb in the boot.ini file?SQL is consuming 2.3GB of memory
April 17, 2013 at 3:32 pm
I could see PAE is enabled in the boot.ini file as this is the 64 bit machine. Can you please suggest me removing of the PAE from boot.ini and adding /3gb is fine?
April 17, 2013 at 4:02 pm
prashanthreddymr (4/17/2013)
Is reboot of the server required after adding /3gb in the boot.ini file?SQL is consuming 2.3GB of memory
yes a reboot is required.
Where did you get the 2.3GB reading from, that suggests the 3GB switch is already enabled otherwise I would expect the reading to be about 1.7GB.
---------------------------------------------------------------------
April 17, 2013 at 4:03 pm
prashanthreddymr (4/17/2013)
I could see PAE is enabled in the boot.ini file as this is the 64 bit machine. Can you please suggest me removing of the PAE from boot.ini and adding /3gb is fine?
yes its fine
---------------------------------------------------------------------
April 17, 2013 at 4:08 pm
I got it from the Mem Usage in the windows task manager where sqlserver.exe is consuming this 2,593,424K
April 17, 2013 at 11:08 pm
If SQL is consuming 2.3 GB, and if you see /3G switch already enabled, why you want to remove ?
If you have 4 GB of RAM, I would go setting SQL Max memory to 3200 MB (I believe its recommended) and the leave rest for OS.
Hope this helps..
Cheers,
- Win
"Dont Judge a Book by its Cover"
April 17, 2013 at 11:54 pm
prashanthreddymr (4/17/2013)
I could see PAE is enabled in the boot.ini file as this is the 64 bit machine. Can you please suggest me removing of the PAE from boot.ini and adding /3gb is fine?
If it's a 64-bit OS then /3GB is not needed (nor is /PAE), just set SQL's max server memory to 3 GB.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 18, 2013 at 12:58 am
And, Windows Server 2003 onwards, I think /PAE automatically get added in boot.ini. So you wont have to remove it as it is just fine if OS is 64 bit.
You have to restrict max memory for SQL as Gail suggested to prevent SQL from using all of the available memory.
Thanks,
Vikas
April 19, 2013 at 3:53 am
Which MaxValue needs to be set, if I got Analysis Services running on the same machine?
Greetz
Query Shepherd
April 23, 2013 at 6:50 am
prashanthreddymr (4/17/2013)
Am a junior DBA and We have an issue from last couple of days. We have a server of Windows 2003 Standard Edtion of x64 bit with SP2. SQL Server is of 32bit running. Physical Memory on the server is 0f 4GB and SQL now running out of memory. Can we enable the AWE on a 64 bit OS machine where SQL is of 32 bitPlease suggest me
64-bit Windows with a 32-bit SQL Server instance running on it is not a typical configuration. You do not need to worry about /PAE or /3GB on a 64-bit OS. If you have either in your boot.ini you should
consider removing it. Just set max memory to 3GB for the SQL Server instance. On a 64-bit OS a 32-bit instance of SQL Server can use up to 4GB of memory without any additional configuration:
EXEC sys.sp_configure
@configname = 'max server memory (MB)',
@configvalue = 3072;
GO
RECONFIGURE;
GO
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply