"Todd C" wrote:

> Nigel:
>
> Can you elaborate on how you would handle transferring history rows to a
> table? I am in pretty much the same situation as Mike (Reporting Services
> subscriptions and BizTalk processing jobs tend to fill up the job logs).
>
> SSIS or some other easy to use command?
> Where do we find the logs?
> Does it matter where the table is stored?
> How do I keep from adding the same row twice from the log to the table?
>
> Much appreciated!
> --
> Todd Chittenden
>
>
>
> "Nigel Rivett" wrote:
>
> > If you look at the agent properties there is a max total number of rows to
> > keep and a number per job - any more than that will be deleted.
> >
> > I often implement a job to copy history rows to a table.
> >
> > "Mike Torry" wrote:
> >
> > > My SQL jobs used keep their history on SQL Server 2000 MSDB. Recently all
> > > jobs keep losing their job history. Each job only keep some history for very
> > > short period.
> > > Do you know why?
> > >
> > > Thanks,
> > >