June 7, 2011 at 10:36 am
Guys downstairs just built a 2003 Enterprise Server 32bit with 8GB RAM which is Virtual.
I was told to install SQL Server 2005 Standard Edition which from my understanding won't utilize the full amount of availabe memory the server has to offer. I have read that I need to enable AWE in SQL server, /PAE, and the /3GB flag in the boot.ini file. Is it okay to have both /3GB & /PAE flags at the same time?
Does the fact that this is a VM change any other this? Thanks!
June 8, 2011 at 1:10 am
After these flags you can see full memory in your OS level ?
If yes then enable the AWE and lock pages for the SQL Server Service Account and then restart the SQL Server service
Define Max Memory parameter in sql server around 6 GB
Regards,
Syed Jahanzaib Bin Hassan
BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA
My Blog
www.aureus-salah.com
June 9, 2011 at 12:49 am
PAE is required ins case to address memory above 4GB. Rebuilding as 64-bit Windows would remove this option.
With PAE enabled then you can make use of AWE within SQL Server.
The 3GB switch is different. This increases the virtual address space that is available to the application up to 3 GB, and reduces the amount available to the system to between 1 and 2 GB.
For applications that are memory-intensive, such as database management systems (DBMS), the use of a larger virtual address space can provide considerable performance and scalability benefits. However, the file cache, paged pool, and nonpaged pool are smaller, which can adversely affect applications with heavy networking or I/O. Therefore, you might want to test your application under load, and examine the performance counters to determine whether your application benefits from the larger address space.
June 9, 2011 at 5:57 am
Martin Cairney (6/9/2011)
PAE is required ins case to address memory above 4GB. Rebuilding as 64-bit Windows would remove this option.With PAE enabled then you can make use of AWE within SQL Server.
The 3GB switch is different. This increases the virtual address space that is available to the application up to 3 GB, and reduces the amount available to the system to between 1 and 2 GB.
For applications that are memory-intensive, such as database management systems (DBMS), the use of a larger virtual address space can provide considerable performance and scalability benefits. However, the file cache, paged pool, and nonpaged pool are smaller, which can adversely affect applications with heavy networking or I/O. Therefore, you might want to test your application under load, and examine the performance counters to determine whether your application benefits from the larger address space.
Outstanding! Thanks Martin. Just what I wanted to know.
June 9, 2011 at 7:54 am
1) you do NOT want /PAE on with /3GB.
2) why in the world is someone building a windows server 2003 box in this day and age?? it was a SUCK *** OS compared to win server 2008+.
2) likewise, why in the world is someone building a 32bit server?
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
June 9, 2011 at 10:55 am
TheSQLGuru (6/9/2011)
1) you do NOT want /PAE on with /3GB.
Kevin,
as I have not run into this situation, I am genuinely curious. What's the downside of running both at the same time?
June 9, 2011 at 11:24 am
Check out this FAQ:
5. How do I configure SQL Server to use larger memory space over 2GB on a 32-bit server?
June 9, 2011 at 11:41 am
So it's just that it will cause SQL Server to not use all the physical memory, not that it will cause the Zombiepacolypse or something equally horrendous, right?
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply