title: SQL Server Indexing best practice (SQL Server 2008)
body: <p>I have some doubts on choosing the right index and have some questions:</p>
  
  <p><strong>Clustered index</strong></p>
  
  <p>What is the best candidate?</p>
  
  <p>Usually is the primary key but if the primary key is not used in the search by eg <code>CustomerNo</code> is used to search on customers should the clustered index put on <code>CustomerNo</code>?</p>
  
  <p><strong>Views with SchemaBinding</strong></p>
  
  <p>If have a view with indexes I read that these are not used but those on tables are.</p>
  
  <p>Pointless no? Or am I missing the point? Will it make a difference using "NOExpand" to force to read the index from the view rather than the table?</p>
  
  <p><strong>Nonclustered indexes</strong></p>
  
  <p>Is it good practice when adding a nonclustered index to include every possible column till you reach the limit?</p>
  
  <p>Many thanks for your time. I am reading massive database and speed is a must</p>