June 19, 2013 at 2:00 am
Hi,
Our SQL server services got restarted last night due to memory pressure. Looking forward for your help in diagnosing the issue and finding a resolution.
About our environment:
SQL 2008 SP1 on Windows 2003 R2 SP2 (VM) with 6GB RAM. Its running on a cluster (active/passive). The cluster service had restarted SQL services on the same active node after the incident.
Event Viewer Logs:
1. There is insufficient system memory in resource pool 'internal' to run this query.
2. SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems.
3. [sqsrvres] ODBC sqldriverconnect failed
4. [sqsrvres] CheckServiceAlive: Service is dead
The cluster service had restarted the SQL service after these errors.
Attached are the SQL Server error log and the results of queries (taken from msdn blogs) related to VAS size. Upon examining the logs and query results, it seems the server experienced MTL pressure and the procedure cache is consuming more MTL memory.
Is the diagnosis correct, and if yes, what would be the resolution for this issue?
Thanks
June 19, 2013 at 4:10 am
How long has this been a problem?
Has your SQL Server undergone any major changes either at the instance level or database level?
How much memory is allocated to the offending instance?
What have you tried so far to repair the issue?
June 19, 2013 at 4:13 am
Having seen this entry, could your Windows Server be 32-bit? Or maybe the Windows Server is 64-bit but the SQL Server only 32-bit?
AWE Allocated 4194304
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply