Last post Jun 22, 2018 02:16 PM by RagavanB
Nov 06, 2017 01:57 PM|alok.seth|LINK
I am not sure that this is the right forum to post my query, If not, please let me know.
Earlier we were using ASPState database for managing ASP.NET sessions. With introduction of In-Memory OLTP, there is a post for managing these sessions using In-Memory OLTP structure. Ref (https://blogs.technet.microsoft.com/dataplatforminsider/2014/07/10/new-asp-net-session-state-provider-for-sql-server-in-memory-oltp/).
In old version of ASPState code, there was a facility to manage multiple applications in a single ASPState database using AppId, however with new In-Memory OLTP version, there is no option for AppId.
In our current design, we have 6 different applications using same ASPState database and having different AppId.
So tricky part is we have app groups, which means apps in one group should be treated same for session treatment whereas other group should be creating it's own session and don't interfere with another group.
Could you please help me to handle multiple sessions using new In-Memory structure?
Nov 07, 2017 09:04 AM|Eric Du|LINK
According to your description, about how to use In-Memory with sessions, please check the following tutorials:
SQL Server In-Memory OLTP as ASP.NET Session State Provider:
Introducing SQL Server In-Memory OLTP:
Nov 09, 2017 11:38 AM|alok.seth|LINK
Thanks Eric. We have already looked at these sites during implementation. Only problem we are facing to maintain multiple applications in single ASPState database. Sessions between different applications are being mixed during getting the session information.
In older ASPState code there were option for handle multiple applications using AppId which I do not see anywhere in ASPStateInMemory database.
Jun 22, 2018 02:16 PM|RagavanB|LINK
Does any one have a solution for this? I am also require solution for the above same problem.