«

I heard that using inproc session is not very good idea because it consumes
a lot of memory if there are many users using web at the same time. Is is
true? If so, is there another good (and easy) way to store temp. data
instead of using session?

Thanks

i would never use inproc on any large, active site. besides being a memory
hog, its lost on asp.net recycles. try the sqlserver session manager.

-- bruce (sqlwork.com)

"slavyan" <> wrote in message
news:...
| I heard that using inproc session is not very good idea because it
consumes
| a lot of memory if there are many users using web at the same time. Is is
| true? If so, is there another good (and easy) way to store temp. data
| instead of using session?
|
| Thanks
|
|

You may wish to use SQL Server to maintain session state and or State
Server. There are two methods for SQL Server as session state holder:
Temporary and Persistent: Below is a "how to" article prepared by Microsoft
for your purpose:

http://www.microsoft.com/resources/d...g_dep_wkad.asp

John

"slavyan" <> wrote in message
news:...
>I heard that using inproc session is not very good idea because it consumes
> a lot of memory if there are many users using web at the same time. Is is
> true? If so, is there another good (and easy) way to store temp. data
> instead of using session?
>
> Thanks
>
>