Im using a query against dm_os_ring_buffers in SQL 2005 to find possible evidence of low memory issues.
Credit goes to this author
http://blogs.msdn.com/b/mvpawardprogram/archive/2012/06/04/using-sys-dm-os-ring-buffers-to-diagnose-memory-issues-in-sql-server.aspx
Is it safe to say that if your results include RESOURCE_MEMPHYSICAL_LOW for the ResourceMonitor/Notification values, then you can say - Yes there was a low memory issue at that point in time ?
Looking at a sample of the results below, it appears to me that "something" was on 7/11 around 2:20pm that was chewing up ALOT of memory. Why would we see a constant flip/flop between
RESOURCE_MEMPHYSICAL_LOW and RESOURCE_MEM_STEADY like this?
| RmNotification | IndicatorsProcess | IndicatorsSystem | RmDateTime |
| RESOURCE_MEMPHYSICAL_LOW | NULL | NULL | 7/11/13 2:21 PM |
| RESOURCE_MEM_STEADY | NULL | NULL | 7/11/13 2:21 PM |
| RESOURCE_MEMPHYSICAL_LOW | NULL | NULL | 7/11/13 2:21 PM |
| RESOURCE_MEM_STEADY | NULL | NULL | 7/11/13 2:21 PM |
| RESOURCE_MEMPHYSICAL_LOW | NULL | NULL | 7/11/13 2:21 PM |
| RESOURCE_MEM_STEADY | NULL | NULL | 7/11/13 2:21 PM |
| RESOURCE_MEMPHYSICAL_LOW | NULL | NULL | 7/11/13 2:21 PM |
| RESOURCE_MEM_STEADY | NULL | NULL | 7/11/13 2:21 PM |
| RESOURCE_MEMPHYSICAL_LOW | NULL | NULL | 7/11/13 2:21 PM |
| RESOURCE_MEMPHYSICAL_LOW | NULL | NULL | 7/11/13 2:21 PM |
| RESOURCE_MEM_STEADY | NULL | NULL | 7/11/13 2:21 PM |
| RESOURCE_MEM_STEADY | NULL | NULL | 7/11/13 2:21 PM |
| RESOURCE_MEMPHYSICAL_LOW | NULL | NULL | 7/11/13 2:21 PM |
| RESOURCE_MEMPHYSICAL_LOW | NULL | NULL | 7/11/13 2:21 PM |