title: Is there a reason combining SELECT TOP with OPTION (FAST N) would change the execution plan?
body: <p>This is an example of a query I looked at recently:</p>
  
  <pre><code>SELECT TOP 10 id, name
  FROM example_table WITH(NOLOCK)
  INNER JOIN example_table2 WITH(NOLOCK)
      ON example_table.x = example_table2.id
  OPTION (FAST 10)
  </code></pre>
  
  <p>Assuming the rest of this somewhat unusual query stays the same...is there any reason why adding OPTION (FAST N) would cause a query already using TOP to go any faster, or run any differently? If so, why?</p>