PAE switch

Django x2 · 28 Jan 2010 at 15:03

We're running Windows Server 2003 32bit Enterprise (SP2).

Yes, I know!

We have SQL 2005 running on here and someone suggested whacking in 8Gb and invoking the PAE switch. Now, I know it's fine, but is it really going to work as we hope?

The server is a new build and I'm all for whipping x64 Windows on there but meh

Lucifurr · 30 Jan 2010 at 18:08

Well using the PAE switch would allow Windows to use all 8GB of memory but I am reasonably sure that Windows processes can only grow up to 2Gb because it is still just 32-BIT Windows.

I would use 64-BIT for Windows and SQL Server. Never really see teh point of 32-BIT O/S these days as 32-BIT programs still work on x64 versions of Windows.

Burnsy2023 · 30 Jan 2010 at 18:32

You could get the 32bit process to use up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT

Lucifurr · 30 Jan 2010 at 18:49

Didn't know about that, thank Burnsy

Hoodlum · 30 Jan 2010 at 19:23

Careful with IFLAA though. Can (and does) cause instability with some processes. I don't have a comprehensive list or anything to give you though...

Django x2 · 30 Jan 2010 at 22:01

Burnsy2023 said:
You could get the 32bit process to use up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT

Is this a boot.ini edit too?

Lucifurr · 31 Jan 2010 at 12:59

Yes, you have to put /3GB switch in the boot.ini (better double check the switch) but the process that needs 3GBs needs to be programmed to take advantage of the extra memory. E.g a product I use, BusinessObjects, is not set to take advantage of the extra memory.