Share via

SQL 2008 - New Functionality to the dm_os_ring_buffers for Connectivity Troubleshooting

  • Article

Hi,

 

I wanted to make everybody aware of this feature in SQL 2008. 

 

Are you tired of having to use NetMon to narrow down a connectivity issue with SQL Server 2008 or have to wait for an elusive connectivity error to reoccur?

 

A new ring buffer called "RING_BUFFER_CONNECTIVITY' has been added to the dmv sys.dm_os_ring_buffers in SQL 2008 RTM.

 

This will automatically log server-side initiated connection closures, if you see nothing in the dmv, then most likely the client reset/closed the connection. You can enable any connection closure (client or server) logging with trace flag 7827.

 

Please read this blog for more information!

https://blogs.msdn.com/sql_protocols/archive/2008/05/20/connectivity-troubleshooting-in-sql-server-2008-with-the-connectivity-ring-buffer.aspx

 

So if SQL Server 2008 is still online since the connection failure, make sure to capture the information from the sys.dm_os_ring_buffers base on the query in the blog above, as it may give you enough information to narrow down your troubleshooting to the client or server without costly netmon traces.

 

Hope this helps!

Eric Burgess
SQL Server Escalation Team

Comments

  • Anonymous
    December 28, 2009
    Thank you Eric this is really helpful informaion for me.

  • Anonymous
    December 28, 2009
    Thank you Eric this very helpful iformation for me.

  • Anonymous
    January 03, 2010
    Could you write a follow-up post and give a couple examples of when you'd need to use the trace flag and how to read the results in the table.  I just checked mine and there are 3K entries in it... what am I looking for exactly? Thx.