title: Azure SQL Database - Execution Timeout Expired error on several jobs
body: <p>In SQL Server Management Studio, I discovered an issue while attempting to disable a trigger on one of our tables in our Azure SQL Database, which is set at one of the highest-available performance tiers (Business Critical Gen 5). I used right-click disable to accomplish this.  I receive the following error after the timeout period expires:</p>
  
  <pre><code>Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. (.Net SqlClient Data Provider)
  
          ------------------------------
          For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&amp;ProdVer=12.00.0700&amp;EvtSrc=MSSQLServer&amp;EvtID=-2&amp;LinkId=20476
  
          ------------------------------
          Server Name: searchfoundry.database.windows.net
          Error Number: -2
          Severity: 11
          State: 0
  
  
          ------------------------------
          Program Location:
  
             at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)
             at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType, Boolean retry)
  The wait operation timed out
  </code></pre>
  
  <p>The help link goes to a 404 - no surprise there.</p>
  
  <p><strong>EDIT #1:</strong>
  @DanGuzman kindly assisted me in suggesting I run the disable trigger as T-SQL. This worked.  However, in between the time I originally posted, and the time he gave his suggestion, I discovered that this timeout error is occurring within other areas of our infrastructure/services which use this database. </p>
  
  <p>I have run a query to check for blocking sessions on this database.  There are none listed.  I have also increased the timeout period from 30 seconds to 5 minutes.  Items are still timing out.</p>
  
  <p>I am looking for guidance on what other queries I can run to look under the hood of this database to determine what is causing these timeouts to occur.</p>
  
  <p>I'd be happy to just restart the SQL Server to resolve this, but as many of us know, there is no restarting Azure SQL Servers, unfortunately.</p>