DavidH asked a question.
DUJ ExecutionTime looks wrong
I'm wondering if anybody else has noticed this... the overall ExecutionTime value shown in tblJobLog doesn't seem correct, and doesn't match the LastJobDuration value shown in tblSystemInfo. The value in tblSystemInfo seems to be correct, but the ExecutionTime looks wrong:
I assume that everybody else sees the same difference? For us, it happens on both 9.21.1 and 9.22.1. It seems like tblSystemInfo is a better place to look if you're checking DUJ times in your database... And I suppose this also means that the ExecutionTime values in tblJobLogHistory are wrong as well?
David
Hi David,
Yes, I do also see that.
I do get​ an Email of DUJ Status and in the past wondered, why that mail always came around 10 min after DUJ finished.
Re​cently Snow did a change to this and announced that in Release Notes. Since that time, my Email suits the duration mentioned in tbljoblog, but end time in tbljoblog is not the same like it should be, compared to duration.
Thanks @Carola Iberl​ that's useful to know. We have e-mail monitoring on our DUJ times as well, but we get the duration from the Web API, so the times are accurate. Perhaps I will put this on the ideas board, because it would be less confusing if the durations matched up.
Looking at this on a 9.19.0 environment, the times in both tables are different but only by a few seconds rather than minutes like you have. In some cases it's only out by 1 second.
Actually, that's quite interesting Laim ... because I've never noticed big differences like this before. Perhaps it's a new issue occurring after 9.19.0. Thanks for mentioning that. It will be interesting to hear what happens if that environment of yours gets updated...
An additional remark: DUJ duration time was changed in SLM 9.21.1
Release Notes included this
Data Update Job
• Calculation of DUJ procedure's duration has been modified to be in line with the actual DUJ execution time for most non-enterprise environments. (04525151)
I noticed the difference in tbljoblog and tbljoblogmetrics during my tests and forwarded that to Snow, but they did not change this. It's strange that end time and duration do not match. But for me it is not a problem and as mentioned, now the duration matches up the Notification mail I daily get from SQL Server. So it seems SQL perhaps is doing some additional tasks.
Yes, that makes sense, thanks. It's not a massive issue, but I'd prefer if the numbers matched. I think for me, it's the tblJobLogHistory table that bothers me, because if I try to compare previous DUJs with the current one it's confusing. I do try to keep an eye on it to see if the DUJ is slowing down - which can happen.
I guess the best thing would be to keep a separate history of what's in tblSystemInfo, but it seems a shame to need to do that.
Why don't you use tbljoblogmetrics for comparison?
This table do show the summary.
I normally use this statement, that then also do show me the jobid from tbljobloghistory in case I need to check the details of a job.
use SnowLicenseManager
select h.jobid as HistoryJobID, m.*
from tblJobLogMetrics m
left outer join (select jobid,actionstart from tblJobLogHistory where jobtype='job_run') h on m.StartTime=h.ActionStart
-- where m.jobdate >= '2022-05-30'
order by jobdate desc
Thanks, that's a nice query. I normally use tblJobLogHistory because it's easy and it's become a habit ;-) But it's good timing because I'm about to look at our indexes to see if we can get the DUJ to go a bit faster in one of our environments...