Many a times there are needs to figure out if really there are instances where SQL Server components were raising Out-Of-Memory conditions. A quick way to keep track of this is to track the ring_buffers table. Typically you will use something like this:
1: SELECT
2: record
3: FROM
4: sys.dm_os_ring_buffers
5: WHERE
6: ring_buffer_type = 'RING_BUFFER_OOM'
Obviously a row here means you do have memory pressures that were being forced. For some explanation on the various values ring_buffers might send, see this blog post from PSS which gives you some starters. I highly recommend reading this whitepaper in your leisure for Performance Troubleshooting which also talks about some of the cool things ring_buffers expose when you start working with SQL Server.
Happy weekend 
…
This entry was posted on Saturday, August 28th, 2010 at 01:57 and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
