Convert ASPStateTempSessions table to In-Memory optimized for sqlServer mode SessionSate (For Sql Server 2014). RRS feed

  • Question

  • User-79977429 posted


    I'm using sqlServer mode for sessionSate of my webApp, but performance is very slow! to do this, i found out we can convert 'ASPStateTempSessions' table to in memory optimized table to increase performance. To do this, i found this link, but it works for sqlServer 2016 whereas i'm looking for 2014.

    Can anybody help me ?

    thanks in advance

    Thursday, May 30, 2019 7:55 PM

All replies

  • User1724605321 posted

    Hi hamed_1983,

    The recommended approach is to use  use the latest ASP.NET async version of the SQL Session State provider:

    ASP.NET Session State with SQL Server In-Memory OLTP

    I would suggest try the latest async version of sql session state provider .

    Best Regards,

    Nan Yu

    Friday, May 31, 2019 2:18 AM
  • User-79977429 posted

    Thanks for reply

    I'm using vs 2015 and does not have 4.6.2 version of .net, the maximum version is 4.6.1.

    Also in option2, As i told in my first post, using vs 2016 compatible script, not 2014 which i'm using!

    Friday, May 31, 2019 7:45 AM
  • User1724605321 posted

    Hi hamed_1983,

    You probably need to install the 4.6.2 SDK. It includes the reference assemblies for 4.6.2, which is what Visual Studio needs in order to target 4.6.2 for builds.

    SDKs for all .NET versions (3.5+) are available from the .NET SDKs for Visual Studio page.

    I also not find sql script which compatible with sql server 2014.

    Best Regards,

    Nan Yu

    Wednesday, June 5, 2019 2:34 AM
  • User753101303 posted


    And which problem do you have when trying to run this script ? Note that prior to SQL Server 2016 SP1, you need the Enterprise edition to use the "in memory" feature. (edit: seems the WITH NATIVECOMPILATION option is perhaps not possible in SQL Server 2014 when using memory optilmized tables ????)

    I would also install 4.6.2 to have a test app up and running as close as possible to out of the box features. And if I'm forced to stick to 4.6.1 I could then compare to see how to possibly port back that to my 4.6.1 version (apparently they added async support as well for the session provider) but I guess that upading the old proc might be enough.

    Wednesday, June 5, 2019 11:50 AM