Well, how used are the statements with the joins? If 5+ inner joins are the cornerstone of your web application which every visitor will be thrice per visit, then denormalize! There's no way you can make up for that kind of a performance sap.<BR><BR>Otherwise, you're probably making up for the joins by ensuring that your very-used queries don't have to sort through all of the rows which would be caused by non-normalized statemtents.<BR><BR>My suggestion is to figure out which queries are the most common (try to get it down to one or two), and de-normalize your database based on the Joins used in those. That should improve performance -- at the cost of certain database features which you may not have been using anyway.
Or simply use ADO 2.x Data Shaping as explained at:<BR><BR>http://www.4guysfromrolla.com/webtech/092599-1.shtml<BR><BR>I think it may alleviate some of the pain in the cases<BR>where you cannot de-normalize.