I'm experiencing performance issues on my ASP.NET application. Sometimes it takes 30-40 seconds to run the command, where sometimes it takes 3-4 seconds I tried the SQL Profiler and I do not see any problem. I was not able to repeat this issue in my favor, in the same situation the customer was trying when.
I am thinking that this session is using the variable. I'm using them to pass information inside a lot of pages. Although I do not clean them.
If I clean them, will it help? And if it would affect other users or is it just clear to that user?
Any help is appreciated.
Locking a record in one of the procedures stored in the .NET 2.0 implementation of SQL Server-based session storage There was a problem. It seems that MS has included a diagnosis in the .NET 4.0 release.
Take a look here:
I'm 99% sure you can run version 4.0 of aspnet_regsql -ssadd and still ASP against it. I remember that making a difference of 2.0 vs. 4.0 SQL script was the only real difference. MS 'implementation of privacy was slightly better than the link above (and clearly based).
Comments
Post a Comment