sql-session-state

问题 I'm not a fan of using ASP.NET session state, but our application is using it at this time. We are using SQL Server mode for session state persistence. I'm considering caching authorization check results in the session state, but I worry about the performance of this approach. How exactly does SQL Server session state persistence work in .NET? From what I can tell, all session data is stored in one database row, with the data itself stored in one column. My worry is that if our application

问题 I have two applications deployed on different servers. 1) ASP.net MVC 4 web application with sessionState mode="SQLServer" for session management 2) Servicestack service application with sessionState mode="SQLServer" for session management ( yes i need session in service application ) both application share same database and tables for session management I am using following solution to have asp.net session in service stack application . Reconnecting to Servicestack session in an asp.net MVC4

问题 I have a ASP.NET MVC workflow configured as two websites managed by a load balancer. The websites use Sql Server as the session state provider and have authentication switch off (its not required). Now, sporadically I appear to be losing session state, and I believe this is because the request is being handled by the alternative server, so essentially the user is jumping from server to server, depending how the load balancer sees fit. I am not always "losing session state" at the same stage