Search

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

Active

4
0
Sign in
 to vote
Type: Bug
ID: 485232
Opened: 8/25/2009 11:06:25 PM
Access Restriction: Public
1
Workaround(s)
1
User(s) can reproduce this bug
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 (expand)
Product Language
English

Version

SQL Server 2008 R2 August CTP

Category

Tools (SSMS, Agent, Profiler, etc.)

Operating System

Win2003 Enterprise Server (SP2)
Operating System Language
US English
Steps to Reproduce
Open SSMS --> Connect to a database server(local or remote running SQL 2k8 R2) --> Right click on SQL SERVER AGENT --> Go to the History tab

Under this, check the box for activating 'Remove Agent History' and make changes to the field for 'Older than'.
Once these changes are made, click 'OK' and quit.

Go back to the same screen, and the changes made are not reflected.

This change doesnt reflect even after restarting the agent services.
Actual Results
Once the changes are made to the 'Remove Agent History' settings and we click ok and quit the screen.
Go back to the same screen, and the changes made are not reflected.
This change doesnt reflect even after restarting the agent services.
Expected Results
Once the changes are made to the 'Remove Agent History' settings and we click ok and quit the screen.
Go back to the same screen, and the changes made should take effect.

Platform

X64
File Attachments
0 attachments
Sign in to post a comment.
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
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement