title: RING_BUFFER_CONNECTIVITY - LoginTimers - Error 17830 logs when releasing unused database connection in MSSQL
body: <p>I have this program  that uses QLOLEDB (also tried using the MSOLEDBSQL) to connect to local sql server express 2014 (ver 12.0.2). The program always creates 2 connections, one for IDBCreateCommand and one for iOpenRowset which is used for fastload. The program is functioning well but it keeps on creating RING_BUFFER_CONNECTIVITY LoginTimers logs in sys.dm_os_ring_buffers when I try to release the database connections. No error were created in SQL server logs.</p>
  
  <p>Using the SQL profiler, I know that the logging of RING_BUFFER_CONNECTIVITY happens during Audit Logout of the database connection, though I have 2 connections, only one of them is creating the RING_BUFFER_CONNECTIVITY log and it only happens when releasing connections that were not use (does not matter if it is using IDBCreateCommand or iOpenRowset). Using connections for running SQL query will not log RING_BUFFER_CONNECTIVITY when they are released.</p>
  
  <p>The issue is also happening in MS SQL server 2016 express (ver 13.0.4001) but not in MS SQL server 2012 express(ver 11.0.5058), I am really running out of ideas as to what is causing this. Is there some added feature in SQL server 2014 and later versions that warns user of unnecessary database connections that were created? Like connections that were created but not even use? (I tried proving this by creating database connections using MS SQL management studio then closing it afterwards and it does not create a RING_BUFFER_CONNECTIVITY log... but looking at the sessions created using OLEDB and MS SQL management studio in sys.dm_exec_sessions.. sessions created using OLEDB has memory_usage = 0, while the latter has memory_usage = 3).</p>
  
  <p>What am I missing?</p>
  
  <p>Attached is the sample record created in sys.dm_os_ring_buffers.</p>
  
  <p><img src="https://i.stack.imgur.com/X9Ign.png" alt="ring_buffer_connectivity_log"></p>