title: SQL Server vs .Net Client - Best practice of returning Huge Data from server - Performance Improvement
body: <p>I am attacking performance issues in an Enterprise application. One of my SQL Proc returning More than 2 MB of data (XML plain text).  For executing that SP Its taking around 600 ms only with in the DB server. But, Its taking around 30 seconds to get response in my UI.</p>
  
  <p><strong>SQL server 2008 / .NET 4.0  (IIS hosted windows application)</strong></p>
  
  <p>Note :  In previous performance iterations - Too many DB calls clubbed together and hence avioded many DB calls. But now returning data is huge and facing this issue.</p>
  
  <p>Please help on to identify any standard or restrictions best practices available here to improve performance.</p>
  
  <p>Based on the comments received below thought of add this here:-</p>
  
  <ol>
  <li>But I have found this while I am executing the same Sp call from my local SQLserver Query analyser with connectivity of onsite server. 2. Its not a intranet, but communication between US/India through Internet. 3. I analysed thouroughly using dottrace tool and source too. 4. There is no bottle neck of binding this data. Previousely around 15 Db calls were there with in Loop (every call carries small # of Kbs), but now reduced in to clubbed single call but carries large Data in MB.</li>
  </ol>
  
  <p>Regards,
  Karthikeyan.G</p>