title: SqlException timeout expired without being reached
body: <p>From time to time our server throw this well-known exception:</p>
  
  <p><em>Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.</em></p>
  
  <p>This happens under pressure when the server is working on big requests.
  I did some research and found out that I could change <strong>connection string connection timeout</strong> setting and/or <strong>SqlCommand.Timeout</strong> data reader properties.</p>
  
  <p>By default, sql command timeout is set to <strong>30</strong> seconds and connection timeout to <strong>15</strong>, and we never override them.</p>
  
  <p>I reproduced the context and executed the failling requests by hand in management studio.
  Their duration are <strong>around 1</strong> second and always <strong>far beyond 30</strong>.</p>
  
  <p>But strangely when I take a look at the server logs, this exception is thrown right away the request call.
  I mean, the request is executing and one millisecond later the exception is raised.
  Excuse me but let me do my geek look about this <strong>8-o</strong>.</p>
  
  <p>To be complete, our sql instance is mirrored with another one in <strong>synchronous mode</strong>.
  We use Ado.Net through table adapters.</p>