>In most cases you can count on Serialization being faster than going back to the backend...
>
>However, the right place to dump this stuff more likely is going to be the Cache object for most reusable things. Storing data on a per user level is going to be too fat for most applications - too much data stored memory (with both InProc and StateServer state stores).
>

Why wouldn't you just use SQLServer state store for the serialized objects? I don't quite understand the point of creating your own table and storing the session data in your table, where you will have to access the database on each page request.

Morgan