title: How does ADO.NET Connection Pooling work with .ASMX Web Services?
body: <p>I've created an old-style .ASMX web service and would like to know how the built-in ADO.NET connection pooling works with it.</p>
  
  <p>The web service is not using a singleton pattern, so it is instantiated anew with every request.  My question is will connections be removed from the pool after each service request, or are they kept in the pool across requests?  My service is called very frequently but I don't want to be doing setup and teardown of connections every time, if it can be avoided.</p>
  
  <p>I have read that the pool is maintained for the AppDomain, but I'm not sure if each request generates a new AppDomain or not.</p>
  
  <p>I am also curious if it would be beneficial to set Min Pool Size (to a small number other than 0) in this case.</p>
  
  <p>Anyone know?</p>