title: Azure SQL Data IO 100% for extended periods for no apparent reason
body: <p>I have an Azure website running about 100K requests/hour and it connects to Azure SQL S2 database with about 8GB throughput/day.  I've spent a lot of time optimizing the database indexes, queries, etc.  Normally the Data IO, CPU and Log IO percentages are well behaved in the 20% range.  </p>
  
  <p>A recent portion of the data throughput is retained for supporting our customers.  I have a nightly maintenance procedure that removes obsolete data to manage database size.  This mostly works well with the exception of removing image blobs in a varbinary(max) field.  </p>
  
  <p>The nightly procedure has a loop that sets 10 records varbinary(max) field to null at a time, waits a couple seconds, then sets the next 10.  Nightly total for this loop is about 2000.</p>
  
  <p>This loop will run for about 45 - 60 minutes and then stop running with no return to my remote Sql Agent job and no error reported.  A second and sometimes third running of the procedure is necessary to finish setting the desired blobs to null.</p>
  
  <p>In an attempt to alleviate the load on the nightly procedure, I started running a job once every 30 seconds throughout the day - it sets one blob to null each time.  </p>
  
  <p>Normally this trickle job is fine and runs in 1 - 6 seconds.  However, once or twice a day something goes wrong and I can find no explanation for it.  The Data I/O percentage peaks at 100% and stays there for 30 - 60 minutes or longer.  This causes the database responsiveness to suffer and the website performance goes with it.  The trickle job also reports running for this extended period of time.  If I stop the Sql Agent job, it can take a few minutes to stop but the Data I/O continues at 100% for the 30 - 60 minute period.</p>
  
  <p>The web service requests and database demands are relatively steady throughout the business day - no volatile demands that would explain this.  No database deadlocks or other errors are reported.  It's as if the database hits some kind of backlog limit where its ability to keep up suddenly drops and then it can't catch up until something that is jammed finally clears.  Then the performance will suddenly return to normal.</p>
  
  <p>Do you have any ideas what might be causing this intermittent and unpredictable issue?  Any ideas what I could look at when one of these events is happening to determine why the Data I/O is 100% for an extended period of time?  Thank you.</p>