• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

2003 64bit server VMware issues

mrCide

Diamond Member
Anyone here have experience with a high resource 2003 64bit VM?

We're running ESX 3.5, the VM has 16GB RAM assigned as well as 4 CPUs (our blades are dual 4 core CPUs w/32GB ram so physical resources are there).

We're running SQL on this server, nothing else, and experiencing strange virtual memory issues. Server has crashed several times because it basically ran out of virtual memory. Physical resources were fine, even task manager did not show any excessive usage, sql, everything looked fine. Same with CPU utilization. Just virtual memory. We've re-sized from 2-4gig dynamic swap to a static 8 and still experienced issues crashing due to running out of virtual memory. Almost like it's being used then locked and not released.. if that's even possible

At this point I created a new virtual drive that's 55 gigs and allowed system to size swap file on that partition as it wants, but the issue bugs me. Is there a bug or am I just missing something? I'm pretty sure that the "swap must be 1.5-2x the size of your RAM" thing is outdated.

I know it's a stretch but anyone experienced with an environment like this?
 
Is SQL Server 32-bit or 64-bit? Do you have a limit on memory usage set in SQL server? Have you monitored the SQL Server process to see how much virtual and physical memory it's using before it crashes?
 
Heh, forgot to check back on this. SQL server is 64-bit as well. Limit was set to 14 gigs for SQL (of the 16 physical available). I see no physical issues, including the sql process, that show any indication of issues.

After a couple weeks with that system sized swap file it was reaching over 32 gigs in size before someone restarted the server. Just increases and increases regardless of size until the server crashes.
 
Back
Top