Connectivity troubleshooting in SQL Server 2008 with the Connectivity Ring Buffer
Published Mar 23 2019 05:21 AM 4,877 Views
First published on MSDN on May 20, 2008

SQL Server 2008 contains a new feature designed to help troubleshoot particularly tricky connectivity problems. This new feature, the Connectivity Ring Buffer, captures a record for each server-initiated connection closure, including each kill of a session or Login Failed event. To facilitate efficient troubleshooting, the ring buffer attempts to provide information to correlate between the client failure and the server’s closing action. Up to 1k records in the ring buffer are persisted for as long as the server is online, and after 1000 records, the buffer wraps around and begins replacing the oldest records. The Connectivity Ring Buffer’s records are exposed by a DMV which can be queried:

SELECT CAST(record AS XML) FROM sys.dm_os_ring_buffers

This will select all records as XML types; in Management Studio, you can click the records to get a more readable version. If you want to use SQL queries on the XML records to locate your particular problem, you can also use SQL Server’s XML support to turn this into a temp table and query against the records.

A basic ring buffer entry: killed SPID

An easy way to cause a server-initiated connection closure is to open two connections to a SQL Server, find the SPID of one of the connections, and then kill that spid from the other connection:

C:>osql -E
1> SELECT @@spid
2> go
(1 row affected)

C:>osql -E
1> kill 51
2> go

If you try this and then query the ring buffer, you will get a result which will look like this:

<Record id="2" type="RING_BUFFER_CONNECTIVITY" time="110448275">







<RemoteHost>&lt;local machine&gt;</RemoteHost>


<LocalHost />


<RecordTime>5/6/2008 22:47:35.880</RecordTime>

















<frame id="0">0X01CA0B00</frame>

<frame id="1">0X01CA0DB1</frame>

<frame id="2">0X01DF6162</frame>

<frame id="3">0X02E53C98</frame>

<frame id="4">0X02E54845</frame>

<frame id="5">0X02E57BE9</frame>

<frame id="6">0X02E38F57</frame>

<frame id="7">0X02E3B2C0</frame>

<frame id="8">0X02E3C832</frame>

Version history
Last update:
‎Mar 23 2019 05:21 AM
Updated by: