In ASP.NET, there are 3 different modes for storing session information:
- InProc
- StateServer
- SQLServer
At DiscountASP.NET, we support both InProc and SQLServer session. By default, ASP.NET session is stored in-process (InProc).
There are pros and cons for these modes.
InProc mode offers the fastest performance because session is stored in the IIS Worker Process. The downside of InProc session is that sessions can be lost if the worker process is recycled for any reason.
SQL Server session on the other hands is slower than InProc, about 15-20% slower, but the session information remains persistent even after the worker process is recycled.
You should choose an appropriate state management mode depending on your application. For example, if losing session is not acceptable, you should consider using SQL Session rather than InProc.
To enable SQL Server Session, follow the steps below.
- While not required, we recommend purchasing a new MS SQL database in the MS SQL manager to avoid potential conflicts
- Create a support ticket to request an installation. Include the Database name and the version of ASP.NET you are using.
- You will receive an email as soon as the Session State database schema is created
- Update your web.config file as follows
< sessionState
mode="SQLServer"
allowCustomSqlDatabase = "true"
sqlConnectionString="data Source=<SQLSERVERNAME>;database=<SQLDATABASENAME>;user id=<SQLUSER>;password=<SQLPASSWORD>"
cookieless="false"
timeout="15"
/>
- Session information should be stored in your SQL database now
Note that the database schema for the session database is slightly different between ASP.NET 1.1 and 2.0. If you change the framework version, we may need to recreate the database schema for you.
If you run into problems when using this code, please post in our
community forum.
Technical support is unable to assist with specific coding issues.
Article ID: 334, Created On: 11/24/2008, Modified: 4/13/2010