Partager via

ASP.NET, SQL Server Session State, and SQL Server Service Pack 3.....

  • Article

ASP.NET, SQL Server Session State, and SQL Server Service Pack 3 are a recipe for problems. Just a heads up but apparently there are some cross database ownership issues, introduced by SQL Server Service Pack 3, that will cause your database user to no longer be able to read and write to the temporary Session State tables.

Read about the problem and fix here.

Comments

  • Anonymous
    August 07, 2003
    What you did was run the script that creates ASPState and has the SPROCS in it and uses TempDB. When you failover in a cluster or bounce the server you'll encounter these problems. A better fix is to not use TempDB. Simply run UnInstallSqlState.sql and run the script InstallPersistSqlState.sql from Microsofts website. It will no longer use TempDB. It will use ASPState which your user will have access to read/write/create/destroy tables as needed by the session services.