Job history - After the limitation 0f 1000 entries

Hi,
Can some tell me what the behaviour on the refreshment on the job history
when it reaches the limitation of 1000 entries?
Is it flushing all ( and start over from scratch ) or does it use FIFO (
first in first out ).
Guus Kramer
FIFO
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Guus Kramer" <Guus Kramer@.discussions.microsoft.com> wrote in message
news:C24E8EF8-BCEE-4E44-94F7-8A06578504A9@.microsoft.com...
> Hi,
> Can some tell me what the behaviour on the refreshment on the job history
> when it reaches the limitation of 1000 entries?
> Is it flushing all ( and start over from scratch ) or does it use FIFO (
> first in first out ).
> Guus Kramer
|||Just wondering why the log history has vanished when no other actions have
occured. This happens on a random server and is not prodictable.
Any idea?
Guus
"Tibor Karaszi" wrote:

> FIFO
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Guus Kramer" <Guus Kramer@.discussions.microsoft.com> wrote in message
> news:C24E8EF8-BCEE-4E44-94F7-8A06578504A9@.microsoft.com...
>
|||Are you telling me that you get 0 from below query?
SELECT COUNT(*) FROM msdb.dbo.sysjobhistory
If so, you should find out who it emptying the job history. If not, then you have some job which is
executing frequently enough to hit the limit in a way that the other job's history is all aged out.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Guus Kramer" <GuusKramer@.discussions.microsoft.com> wrote in message
news:F9DC2715-4F0A-44C8-B8C9-84A8D054A819@.microsoft.com...[vbcol=seagreen]
> Just wondering why the log history has vanished when no other actions have
> occured. This happens on a random server and is not prodictable.
> Any idea?
> Guus
> "Tibor Karaszi" wrote:
|||The job history table is also limited by space in msdb. Expand the msdb
database manually and you will hold a longer job history.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Guus Kramer" <GuusKramer@.discussions.microsoft.com> wrote in message
news:F9DC2715-4F0A-44C8-B8C9-84A8D054A819@.microsoft.com...[vbcol=seagreen]
> Just wondering why the log history has vanished when no other actions have
> occured. This happens on a random server and is not prodictable.
> Any idea?
> Guus
> "Tibor Karaszi" wrote:
|||Tibor / Geoff,
You're both right...
SELECT COUNT(*) FROM msdb.dbo.sysjobhistory
contains 1000 entries but this is serverwide. on some servers 40 to 50 jobs
are running and some of them each 5 minutes. So the job history can be aged
out ( and dissapear ) for some jobs when logging other history.
Expanding the msdb database seems to be the only option on this.
Thank you guys for giving me input on this.
Guus Kramer
The Netherlands
"Guus Kramer" wrote:
[vbcol=seagreen]
> Just wondering why the log history has vanished when no other actions have
> occured. This happens on a random server and is not prodictable.
> Any idea?
> Guus
> "Tibor Karaszi" wrote:
|||... and configure Agent to keep > 1000 rows totally...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Guus Kramer" <GuusKramer@.discussions.microsoft.com> wrote in message
news:8F7E2067-45C6-48B0-85C0-00297BCD078E@.microsoft.com...[vbcol=seagreen]
> Tibor / Geoff,
> You're both right...
> SELECT COUNT(*) FROM msdb.dbo.sysjobhistory
> contains 1000 entries but this is serverwide. on some servers 40 to 50 jobs
> are running and some of them each 5 minutes. So the job history can be aged
> out ( and dissapear ) for some jobs when logging other history.
> Expanding the msdb database seems to be the only option on this.
> Thank you guys for giving me input on this.
> Guus Kramer
> The Netherlands
> "Guus Kramer" wrote: