2005 msdb database size

SQL Server 2005
I noticed that the size of the msdb database on a 2005 server had grown to
about 3-4 times the size of every other server in the farm. When I
investigated, I found:
sysmaintplan_log : 34,315 rows (entries from 10/15 - 11/08)
sysmaintplan_logdetail : 34,267 rows
When I went to the SQl Server Agent properties dialog box, it was set to
limit the size of the job history log to 1,000 & 100 (for any one job). The
Automatically remove agent history dialog is unchecked.
First, am I comparing the correct tables to the correct options (I think I
am).
Second, do I need to enable the 'Automatically remove agent history' to keep
the size of the logs down, or are the options to limit the number of rows
supposed to do that for me?
Addendum: When I enable the "Automatically remove agent history" check box
and click OK, then reopen the properties dialog, the setting was not saved.
"Jay" <nospam@.nospam.org> wrote in message
news:%23ssh81jIIHA.4712@.TK2MSFTNGP04.phx.gbl...
> SQL Server 2005
> I noticed that the size of the msdb database on a 2005 server had grown to
> about 3-4 times the size of every other server in the farm. When I
> investigated, I found:
> sysmaintplan_log : 34,315 rows (entries from 10/15 - 11/08)
> sysmaintplan_logdetail : 34,267 rows
> When I went to the SQl Server Agent properties dialog box, it was set to
> limit the size of the job history log to 1,000 & 100 (for any one job).
> The Automatically remove agent history dialog is unchecked.
> First, am I comparing the correct tables to the correct options (I think I
> am).
> Second, do I need to enable the 'Automatically remove agent history' to
> keep the size of the logs down, or are the options to limit the number of
> rows supposed to do that for me?
>
>
>