title: Getting the connection pool error even when setting the connection string property Pooling to false
body: <p>I am having some connection pool issues in my <strong>sharepoint</strong> application. Every time that my application tries to fetch some data from an SQL Server 2008 R2, I got this exception:</p>
  
  <p>"<strong>Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.</strong>"</p>
  
  <p>I know that I am probably having connections leak problems, but I have checked all parts of my code that I am accessing the database, and all of them are implemented with the <strong>using()</strong> pattern. My SQL Server version is 2008 R2 Express, so I don't have the Profiler Tool to see how many connections my application is actually creating.</p>
  
  <p>I have tried disable the pooling setting the <strong>Pooling=false;</strong> in my connection string, but I've got the same error. Also, I have tried increase the connection timeout and the max pool size with no success.</p>
  
  <p>Inspecting the User Connections on my SQL Server instance before my application get failed using the perfmon, I have got that the number of connections is not even close to 100 (the default max pool size).</p>
  
  <p>One important information is that if I run this application in another computer here in my office, it works perfectly.</p>
  
  <p>Obs: I am using entity context to access the database and this application is not published, I am just run it locally with vs2013.</p>
  
  <p>If you guys know some good way to inspect the connections behavior of my application or have a idea of what could be happening in my development environment, please share with me.</p>
  
  <p>Thanks.</p>