sysjobhistory.run_time issue

[k108]

The sysjobhistory table has a column called run_time, which is the time that a job started to run.

It is an INT column. Times are stored as 5 or 6 digits, usually, which is correct. Such as 20530 or 2:05 am and 30 seconds.

However, sometimes the times show up as less than 5 digits:

3001 or 1, for example. What does this mean?? This is a problem b/c this makes the timestamp less than consistent.

 

[amrita418]

Tis what I think,
3001 --> 00:30:01
1 --> 00:00:01

Since the datatype is int it strips off the leading 0's.

Regards,
AA

 

[k108]

So, you think that these are valid timestamps? I see what you're saying.

Is it possible for SQL Server to make an error, tho?

However, I do see a pattern here, as there are bunches of 3001 in the run times, so there's probably a job running at
12:30 am and 01 seconds.

 

[amrita418]

From what I see, it seems perfectly valid. However, you should test run a job around 12:30:01 and see what you get.

That would be a good test to make sure you assumptions are right.

Regards,
AA

 

[k108]

Yes, thank you