Home Dashboard Directory Help
Search

KJTAP - SAP: SQL SERVER AGENT 'REMOVE AGENT HISTORY' CANNOT BE ACTIVATED by amitgang


Status: 

Active


5
0
Sign in
to vote
Type: Bug
ID: 485232
Opened: 8/25/2009 11:06:25 PM
Access Restriction: Public
1
Workaround(s)
view
2
User(s) can reproduce this bug

Description

When we configure the SQL Agent job history, and try to change the settings or activate the settings for 'Remove Agent History', it lets us change the parameters, and closes the window. However the next time when we open the same property window back again, it doesnt reflect the changes made and goes back to the default settings, where it is not activated.
Details
Sign in to post a comment.
Posted by Ryan B In Seattle on 10/28/2013 at 10:49 AM
Confirming that this bug still exists in v11.0.3000.
Posted by edm2 on 1/5/2013 at 8:12 AM
According to

https://bay002.mail.live.com/default.aspx?id=64855#n=1018898495&fid=1&mid=dd61cd00-569a-11e2-a25a-00215ad7bd84&fv=1

the bug is still not fixed in sql 2012 either.
Posted by EricHoll on 9/15/2009 at 10:35 AM
Correction: Behavior is apparently the same on SQL 2008. Instead of being a config item that you can save, as one would expect, this is actually a real-time cleanup option. As such it would indeed be a design change request, and can be postponed until SQL 11, even though the current design is undesirable. We will have to continue to live with it until then. - Thanks, Eric Holling
Posted by amitgang on 9/14/2009 at 10:30 PM
Hi Amy,
We need this fixed in R2, please check the comments in the community forum by Eric Holling as below:

"This needs to be fixed for R2. We run some jobs like log shipping backup/copy/restore at an interval of every 1 minute. This generates a huge amound of unnecessary log/history records that need to be cleaned up on a regular basis. Our current hardware architecure and msdb location does not support this kind of unrestricted growth. Please re-activate this bug and fix it for the next CTP release. - Eric Holling "
Posted by EricHoll on 9/14/2009 at 4:48 PM
This needs to be fixed for R2. We run some jobs like log shipping backup/copy/restore at an interval of every 1 minute. This generates a huge amound of unnecessary log/history records that need to be cleaned up on a regular basis. Our current hardware architecure and msdb location does not support this kind of unrestricted growth. Please re-activate this bug and fix it for the next CTP release. - Eric Holling
Posted by Microsoft on 9/3/2009 at 9:08 AM
Thank you for your feedback; this is a known issue and I've closed your bug as a duplicate of the work item we are tracking to fix this issue in our next major release.

Thanks,

Amy Lewis
Sign in to post a workaround.
Posted by Dwaine Wright on 8/3/2010 at 12:15 PM
This simply runs an msdb sproc. schedule your own to run....

EXEC msdb.dbo.sp_purge_jobhistory @oldest_date= @adjusteddate