title: good/doesn't matter/bad to include Primary Key in covering index?
body: <p>is is <code>good</code> or <code>doesn't matter</code> or <code>bad</code> to INCLUDE the primary key in a covering index??</p>
  
  <pre><code>CREATE NONCLUSTERED INDEX index_name_here ON dbo.table_name_here
  (column_to_index_here) 
  INCLUDE (primary_key_column,other_column_here)
  WITH( STATISTICS_NORECOMPUTE=OFF, IGNORE_DUP_KEY=OFF, --&lt;default junk from SSMS
  ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
  GO
  </code></pre>
  
  <p>I'm thinking it doesn't matter, since the PK will be in the index anyways.</p>
  
  <p><strong>EDIT</strong> - to clarify.<br>
  my <code>primary_key_column</code> is clustered, but you can explain/give info when it isn't too.</p>
  
  <p>I will be joining to <code>dbo.table_name_here</code> on the <code>column_to_index_here</code> column and will be then joining to other tables on <code>primary_key_column</code> and <code>other_column_here</code>.</p>