July 26, 2007 at 12:46 am
So while I was on vacation, a consultant set up a new server/db with 32bit SQL 2005 on 64bit Windows 2003. Go-live came and went last week, and now I've just discovered this. We've had no problems so far. I've yet to speak with the consultant on whether this was planned or a mistake.
We have a test and a prod server. On test there are 3 instances (QA and DEV, plus a small instance for BackupExec). 8GB RAM total, no AWE enabled, QA=2048MB min/max, DEV=1536MB min/max, BE=128MB min/max. At the moment, 678MB free on the server. On prod, one instance - 3276MB min/max. 8GB RAM total, 1.4GB free. These are SAP servers, and the SAP processes take up most of the memory on each server.
I'm wondering - what happens memory-management-wise with 32bit SQL on 64bit Win? How should SQL be configured in this situation? Should AWE be enabled? What happens without it being enabled? Are there any potential problems?
thanls
July 27, 2007 at 7:45 am
SQL 2005 32 bit will run in the WOW64 subsystem
AWE is not needed and cannot be configured on 64-bit operating systems.
I'm not familiar with SAP servers but i think you should leave your prod server the way it is.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply