title: LINQs Joins vs Stored Procedures Joins
body: <p>I read this <a href="https://visualstudiomagazine.com/articles/2016/12/12/joins-entity-framework.aspx" rel="nofollow noreferrer" title="article">article</a> on using <code>LINQ</code>s for doing <code>Joins</code>.  I was wondering how much  benefit this would be aside from writing a stored procedure that would join the tables?  Would it cause any kind of performance issues using joins with <code>LINQ</code>? </p>
  
  <p><strong>UPDATE:</strong></p>
  
  <p>So using this as an example:</p>
  
  <pre><code>var employeeInfo =
                  from employee in employees
                  join addInfo in additionalInfo on employee.ID equals addInfo.CategoryID into allInfo
                  select new { CategoryName = category.Name, Products = allInfo};
  </code></pre>
  
  <p>Would this simple <code>join</code> benefit me as apposed to a <code>stored procedure</code>?  I know depending on the size of the tables and number of tables you may want to <code>join</code> could make a big difference on when to use <code>LINQ</code> vs <code>store procedure</code>.  What would be a good <em>"rule of thumb</em>" on the number of tables and sizes one should use for <code>LINQ</code> joins and when performing <code>LINQ</code> joins becomes too much of a performance hit?</p>