>Another thing to consider is to use the ASP.Net State Service which is considerably more performant than going to SQL Server as it's optimized to storing state data.

Actually, not that much... most of the overhead is in the serialization and going out of process. The web cast I refered Carl Olson to has some performance comparisons between these scenerios, and byfar an InProc session ruled... to the point of this guy recommending sticky IP's over SessionServer/SQL for this.

BOb