title: Why my ADO.net Connection was Closed but sp_who2 indicates "awaiting command" connections?
body: <p>We are facing serious problems with performance in the database. After making a lot of changes in the procedures, trying to minimize locks, we still have some problems of performance.</p>
  
  <p>When I make a sp_who2 in the database, there are several connections in sleeping mode, "Awaiting command".</p>
  
  <p>Maybe if I close these connections automatically after closing them, we could have a positive impact on the server performance.</p>
  
  <p>And my question is: <strong>How to make connection pooling in ADO.NET close my connections when I call the close, instead of maintaining them in sleeping mode?</strong></p>
  
  <p>PS: I know handling performance is a large topic, we are analyzing more than just this.</p>