title: Multiple queries to avoid joins?
body: <p>I've noticed as soon as I added joins to some of my queries the time it took to execute these was more than just completing multiple queries.</p>
  
  <p>Times include page load and averaged over 20 page loads.  </p>
  
  <p>7-9 queries with no joins<br>
  159ms</p>
  
  <p>3 queries with 2 joins<br>
  235ms</p>
  
  <p>Should I just go ahead with multiple queries instead of the joins considering they seem to have such a significant impact on performance?  I can probably even optimize the multiple query method since I was even lazy loading during those tests.</p>
  
  <p><strong>EDIT</strong></p>
  
  <p>I'll create some false information for sake of the question.</p>
  
  <p>Table Objects<br>
  ID (int, identity, PK, clustered index)<br>
  UserID (int, nonclustered index)<br>
  CategoryID (int, nonclustered index)  </p>
  
  <p>Table Users<br>
  ID (int, identity, PK, clustered index)</p>
  
  <p>Table Categories<br>
  ID (int, identity, PK, clustered index)</p>
  
  <p>Pretty simple.  It's a double inner-join query onto the Objects table.  Querying all 3 separately seems to be faster than the join.</p>
  
  <p>The query plan for the join shows 42% done for 2 clustered index seeks and 23% is a clustered index scan and the rest is a Top N Sort.</p>