treschau...@yahoo.com wrote:
> This is for SQL 2000. Running msdb..sp_help_job will display the
> information. I dug through the msdb..sp_help_jobschedule and put the
> following query together:
>
> select name
> ,cast(left(cast(next_run_date as varchar),4)+'-'+
> substring(cast(next_run_date as
> varchar),5,2)+'-'+right(cast(next_run_date as varchar),2) +' '+
> left(cast(next_run_time as varchar),2)+':'+substring(cast(next_run_time
> as varchar),3,2)+':'+right(cast(next_run_time as varchar),2) as
> datetime) "Next_Run"
> from msdb..sysjobschedules
>
> Converting the next_run_date and next_run_time columns got kind of
> messy, but it works.

treschaud33@yahoo.com wrote:
> treschau...@yahoo.com wrote:
> > This is for SQL 2000. Running msdb..sp_help_job will display the
> > information. I dug through the msdb..sp_help_jobschedule and put the
> > following query together:
> >
> > select name
> > ,cast(left(cast(next_run_date as varchar),4)+'-'+
> > substring(cast(next_run_date as
> > varchar),5,2)+'-'+right(cast(next_run_date as varchar),2) +' '+
> > left(cast(next_run_time as varchar),2)+':'+substring(cast(next_run_time
> > as varchar),3,2)+':'+right(cast(next_run_time as varchar),2) as
> > datetime) "Next_Run"
> > from msdb..sysjobschedules
> >
> > Converting the next_run_date and next_run_time columns got kind of
> > messy, but it works.
>
> This is not as good I hope. If the job isn't going to run until
> tomorrow the next_run_date and next_run_time columns are zero.