title: SQL Server wide indexes with many include columns
body: <p>Should I be careful adding too many include columns to a non-cluster index?  </p>
  
  <p>I understand that this will prevent bookmark look-ups on fully covered queries, but the counter I assume is there's the additional cost of maintaining the index if the columns aren't static and the additional overall size of the index causing additional physical reads.   </p>