C# 2.0 or 3.5 Design best practices for a dashboard application
<p>I am designing a dashboard application (An asp.net web app) where I get the latest updated data in a  grid format. The grid should contain all the real time info. The dataaccess is from most of the tables and may have a 1-many relations and aggregates. So for each record,  I loop thru 100's of tables to get the aggregates of all tables. What are the best practices for designing a dashboard application which is database read intensive. I am expecting more than 1000's to be able to access the app at a time. Any Design patterns I should follow? or any best practices etc.?</p>
