title: ASP.NET: Strategy for handling really large reports
body: <p>Maybe not specific to reports but still...</p>
  
  <p>In my asp.net mvc web application there's a section for reports that show 5 columns of data that map almost directly to a table in the db.</p>
  
  <p>The problem is, in some cases, the length of that report may exceed 40,000 records (I know, nobody can really process 40,000 records of data but the report is what it is) and as you can expect, it times out and throws an error.</p>
  
  <p>The question is, what's a good way to process and deliver a report of that size?  I thought about creating a small little console app that would build the report outside of the webserver but I'm kind of at a loss as to what direction to look into?</p>