Re: Out-of-process State Management Session Cleanup
- From: bruce barker <nospam@xxxxxxxxxx>
- Date: Tue, 11 Sep 2007 17:14:25 -0700
the default session cleanup is a scheduled job with sqlagent. it runs at a specified interval and just deletes expired sessions. if you look at the proc its a pretty simple delete. you could replace it with you own job, that the the session cleanup and ran whatever other code you want.
-- bruce (sqlwork.com)
knyghtfyre@xxxxxxxxx wrote:
Hello,.
My company is developing a rather large application with .NET 2.0. We
are expanding to a server farm and are in the process of converting
our application to use an out-of-process session state management with
SQL Server.
We have ran into a problem with the Session_onEnd event. We know it's
not supposed to fire when in an out-of-process mode, but we have a
large amount of code that must be executed to clean the session and to
log some critical data.
Are there any best practises for dealing with such a situation? What
have others done in the past that have helped them keep a session
state that times-out and cleans up afterwards? Is there a possibility
of the SQL Server to keep track of said timeout and execute some clean
up code?
I've been searching for a few days now and have not yet been able to
find any "best practises" for this type of situation, if you know of
any articles, or have any personal experience, any help is
appreciated.
Thanks,
Marc
- Follow-Ups:
- Re: Out-of-process State Management Session Cleanup
- From: knyghtfyre
- Re: Out-of-process State Management Session Cleanup
- References:
- Out-of-process State Management Session Cleanup
- From: knyghtfyre
- Out-of-process State Management Session Cleanup
- Prev by Date: Re: Where's the code?!
- Next by Date: Re: ASP.NET Threading (It's not showing up!)
- Previous by thread: Re: Out-of-process State Management Session Cleanup
- Next by thread: Re: Out-of-process State Management Session Cleanup
- Index(es):
Relevant Pages
|
Loading