Home/ Questions/Q 7667723
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T15:10:41+00:00

The ASP.NET SQL SessionState provider seems excessive for my requirements. SQL Server has to

  • 0

The ASP.NET SQL SessionState provider seems excessive for my requirements. SQL Server has to be ‘configured’ to support it and I have questions about how optimized it is (i.e. is there one db hit to fetch the whole session or one for every session item requested?).

I think I could implement a custom solution very easily that I would understand and easily redeploy to other projects. Is there something fundamental I haven’t considered here and an obvious reason why the built in SessionState handler is the ‘best’ way to go?

Just to clarify, our applications run on single servers at the moment. My main motivation for doing this is to enable Session to persist across IIS restarts and therefore provide more reliability for users.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    you could use StateServer mode.

    StateServer mode stores session state in a process, referred to as the ASP.NET state service, that is separate from the ASP.NET worker process or IIS application pool.

    Using this mode ensures that session state is preserved if the Web application is restarted and also makes session state available to multiple Web servers in a Web farm.

    more info at http://msdn.microsoft.com/en-us/library/ms178586.aspx

    • 0