Hi, we have a 64 bit server with 6 instances of SQL Server 2008 R2. The server has 32 GB and 12 cores. Each instance is configured to have an upper memory limit of between 1.5 and 6 GB. The primary "dev" instance has an upper limit of 6 GB. The other instances are not normally used much. We received several 2004 events yesterday that indicated that there was not enough virtual space. I could not remote into the machine - the desktop would not display and the screen remained blank. I restarted a few instances remotely (not the dev instance), but was still not able to remote in to the server. Today I am able to remote into the machine. The event log indicated a virtual memory issue occurred yesterday.
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: sqlservr.exe (2196) consumed 114008518656 bytes, sqlservr.exe (3560) consumed 6983954432 bytes, and sqlservr.exe (2284) consumed 5658619904 bytes.
The dev instance was using over a 100 GB of virtual space. The task manager still shows a "Commit Size" of 112 GB. However, the "virtual bytes" performance counter indicates the space is now about 32 GB.
The primary database in use is about 50 GB in size. It is accessed by a MicroFocus product that executes COBOL. A trace reveals attention events that indicate that the code does not always consume all the data before the query is cancelled. (This was the way it worked in DATACOM before the conversion.) This might relate.
The production version of this server has two instances and many more users. The task manager "commit size" is 12 GB for each instance in production.
I could use some advice on how to identify what is the root cause of this issue. If a query is doing this, I would not want it to get migrated to production.
Thanks,Randy
Randy in Marin
