title: SQL Server 2012 Always on has high logcapture wait type
body: <p>From reading, I can see the <code>Work_Queue</code> wait can safely be ignored, but I don't find much about <code>logcapture_wait</code>. This is from BOL, "Waiting for log records to become available. Can occur either when waiting for new log records to be generated by connections or for I/O completion when reading log not in the cache. This is an expected wait if the log scan is caught up to the end of log or is reading from disk." </p>
  
  <p>Average disk sec/write is basically 0 for both SQL Servers so I'm guessing this wait type can safely be ignored?</p>
  
  <p>Here are the top 10 waits from the primary:</p>
  
  <pre><code>wait_type   pct running_pct
  HADR_LOGCAPTURE_WAIT    45.98   45.98
  HADR_WORK_QUEUE 44.89   90.87
  HADR_NOTIFICATION_DEQUEUE   1.53    92.40
  BROKER_TRANSMITTER  1.53    93.93
  CXPACKET    1.42    95.35
  REDO_THREAD_PENDING_WORK    1.36    96.71
  HADR_CLUSAPI_CALL   0.78    97.49
  HADR_TIMER_TASK 0.77    98.26
  PAGEIOLATCH_SH  0.66    98.92
  OLEDB   0.53    99.45
  </code></pre>
  
  <p>Here are the top 10 waits from the secondary:</p>
  
  <pre><code>wait_type   pct running_pct
  REDO_THREAD_PENDING_WORK    66.43   66.43
  HADR_WORK_QUEUE 31.06   97.49
  BROKER_TRANSMITTER  0.79    98.28
  HADR_NOTIFICATION_DEQUEUE   0.79    99.07
  </code></pre>