title: SQL stored procedures with many joins VS many database calls to simple stored procedures
body: <p>I have a general question regarding database performance. I am using DotNetNuke business logic to create business objects and SQL 2008 R2. It's a web application (asp.net/c#).</p>
  
  <p>Consider the following:</p>
  
  <p>I need to load a userprofile that contains alot of information like name, lastname, XP, coins, won, lost, etc etc. Alot of fields from 10 different tables.</p>
  
  <p>I have created one big stored procedure that contains many joins (and nested select/count statements) to get all this information in one database call.</p>
  
  <p>My question is this, is this the correct approach? Or is it better/more performant to make many small database calls to simple stored procedures?</p>
  
  <p>My idea was that it's better to make one databasecall, specially if you start having hundreds of thousands of users. But the joins are starting to be complex and its starting to take some time to load the profile.</p>
  
  <p>Any thoughts? Or ideas?</p>