Long/multiple SQL queries vs Serialization

Question

I'm trying to improve the performance of my web app where a page does a long query to pull data from different tables on a database. It pulls invoice data with multiple item lines, invoice status, and with each line having additional properties from another table.

Is serialization worth considering for improvement? The tables are related and in normalized form.

Answer 1

I’d first do some profiling on the queries just to make sure that they are running as efficiently as they can – simply adding an index in the correct place may solve the problem.

If the queries are fine then I would look at data caching in ASP.NET. The following link is a good article on this: http://aspnet.4guysfromrolla.com/articles/100902-1.aspx