When you look in msdb for the SQL Agent Job duration you will find that it is an int.
This is also the same when you look at
Get-SQLAgentJobHistory from the sqlserver module. (You can get this by downloading the latest SSMS release from here)
This means that when you look at the various duration of the Agent Jobs you get something like this
The first job took 15 hours 41 minutes 53 seconds, the second 1 minute 25 seconds, the third 21 seconds. This makes it quite tricky to calculate the duration in a suitable datatype. In T-SQL people use scripts like the following from MSSQLTips.com
I needed more information than the number of minutes so I have this which will convert the Run Duration to a timespan
So how did I get to there?
First I tried to just convert it. In PowerShell you can define a datatype in square brackets and PowerShell will try to convert it
It did its best but it converted it to ticks! So we need to convince PowerShell that this is a proper timespan. First we need to convert the run duration to a standard length, you can use the PadLeft method of a string to do this which will ensure that a string has a length and precede the current string with a value you choose until the string is that length.
Lets have a length of 6 and preceding zeros PadLeft(6,’0′)
But this works only if it is a string!! Remember red text is useful, it will often contain the information you need to resolve your error. Luckily there is a method to turn an int to a string. I am using the foreach method to demonstrate
Now every string is 6 characters long starting with zeros. So all that is left is to format this with colons to separate the hours and minutes and the minutes and seconds. We can do this with the insert method. You can find out the methods using Get-Member or its alias gm
So the insert method takes an int for the startindex and a string value to enter
There we go now we have some proper formatted timespans however they are still strings. We can then convert them using [timespan] Now we can format the results within the select by using an expression as shown below
and as you can see it is a timespan now
On a slight side note. I needed the durations for Agent Jobs with a certain name within the last 6 days.
I did this by passing an array of servers (which I got from my dbareports database) to
Get-SQLAgentJobHistory. I then used the Where method to filter for JobName and the Job Outcome step of the history. I compared the RunDate property to
Get-Date (today) adding -6 days using the
AddDays method 🙂
Hopefully this will be of use to people and also I have it recorded for the next time I need to do it 🙂