|
Hi All, I have these job(ASPState_Job_DeleteExpiredSessions) running every minute on a few servers and it fills SQL Agent job history and make it hard for me to check things at a glance. I don't exactly understand what the job does but from my quick research on Google i figured it is kind of necessary to delete expired ASP sessions states. So how can I get rid history of the job of the job history page? Also is the job really necessary? Thanks, EDIT: Can I make it run once every hour? Edit: Here is the procedure that the job runs every minute:
(comments are locked)
|
|
What version of ASP.NET are you using? There can be issues with the "shipped" SP that causes blocking/deadlocks. If you are using 2.0 then TEST the SP below. @Jonlee: I am not a developer and I dont know the effect of modifying the SP the way you did. BTW I have no blocking/deadlock issue. What is happening is when I check the SQL agent history every morning for error all I see is successful logs from this job since it runs every minute it bloated the log. so i was wondering if I can run the job once an hour if it doesn't affect anything or if there is a way to limit its logs so that I can see more of log of other jobs. Thanks.
Mar 24 '10 at 12:52 PM
DaniSQL
(comments are locked)
|
|
Dani, Sorry I got the wrong end of the stick. You could change the schedule but on a high volume web server it could cause issue (performance on ASPSTATE db). The filter in the log viewer is limited... You could try using the script below that I have used in the past. Just change the WHERE to exclude your session state job.
(comments are locked)
|

