December 2, 2009 at 6:07 am
I have taken over DBA ownership of a SQL Server 2005 STD ED on Win2003 Ent. Edition 32Bit that was setup by a contractor DBA for another brand we now own. I have never messed with AWE memory settings so any help would be appreciated.
In looking at this SQL Server in the task manager on the server it has 16 gig of memory, the PF was at 13 gig and SQL Server reports only using 230mb of memory. I cannot find what is consuming the 13 gig of memory. The use AWE memory setting is checked but when I look at SP_Configure AWE is not enabled nor is a min/max memory set as directed in BOL. The user base reports things running at a crawl when they run month end processes and in Profiler things don't look that bad so I am thinking memory swap issues and SQL Server starved for memory. I unchecked the use AWE memory and restarted the server and it now shows SQL Server using up to 2 gig of memory as a lets just get back to normal. Has anyone seen this type of behavior of not fully implementing AWE on a 32 bit SQL 2005? Personally as small as these apps are 2 gig of memory will probably work just fine.
December 2, 2009 at 6:47 am
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply