Job scheduler

Hi all
In which table in msdb Database the Executing status of
the job is stored. I need the table name - which holds the
information like
1. Job started.
2. Job executing
3. Job completed info.
The above status may be in the same field of the table
Thanks in advance
Anand.Hi,
Data will be stored in SYSJOBHISTORY table of MSDB database
Column name is : RUN_STATUS
The column hols the below status,
0 = Failed
1 = Succeeded
2 = Retry
3 = Canceled
4 = In progress
Since querying the system table is not advisible , you can execute the
system procedure "SP_HELP_JOBHISTORY" to get the information regarding the
status of each scheduled task.
Thanks
Hari
MCDBA
"Guru S. Anand" <anonymous@.discussions.microsoft.com> wrote in message
news:2d1b01c3fcd6$10b00d80$a001280a@.phx.gbl...
> Hi all
> In which table in msdb Database the Executing status of
> the job is stored. I need the table name - which holds the
> information like
> 1. Job started.
> 2. Job executing
> 3. Job completed info.
> The above status may be in the same field of the table
> Thanks in advance
> Anand.|||Thanks Hari
Anand.

>--Original Message--
>Hi,
>Data will be stored in SYSJOBHISTORY table of MSDB
database
>Column name is : RUN_STATUS
>The column hols the below status,
>0 = Failed
>1 = Succeeded
>2 = Retry
>3 = Canceled
>4 = In progress
>Since querying the system table is not advisible , you
can execute the
>system procedure "SP_HELP_JOBHISTORY" to get the
information regarding the
>status of each scheduled task.
>Thanks
>Hari
>MCDBA
>
>"Guru S. Anand" <anonymous@.discussions.microsoft.com>
wrote in message
>news:2d1b01c3fcd6$10b00d80$a001280a@.phx.gbl...
the
>
>.
>

Job History is missing

I've come into a new SQL server 200o environment and for some reason, none of
the jobs keeps a history past one day. The current production DBA says he has
no idea what's causing it. Does anyone have any experience with this issue?
Thanks in advance.
See if the size of the job history has been limited. This can be found in
Enterprise Manager by selecting your server, going to Management, then right
click on SQL Server Agent and select properties. The Job System tab has
options for limiting the size of the job history log.
Ben Lucas
Lead Developer
Solien Technology, Inc.
www.solien.com
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:881853B8-2F60-4017-8F01-44FBF863BFAF@.microsoft.com...
> I've come into a new SQL server 200o environment and for some reason, none
> of
> the jobs keeps a history past one day. The current production DBA says he
> has
> no idea what's causing it. Does anyone have any experience with this
> issue?
> Thanks in advance.
|||Thanks Ben, that was fast. I think that will do it. Thanks again.
Ed
"Ben Lucas" wrote:

> See if the size of the job history has been limited. This can be found in
> Enterprise Manager by selecting your server, going to Management, then right
> click on SQL Server Agent and select properties. The Job System tab has
> options for limiting the size of the job history log.
> --
> Ben Lucas
> Lead Developer
> Solien Technology, Inc.
> www.solien.com
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:881853B8-2F60-4017-8F01-44FBF863BFAF@.microsoft.com...
>
>