OMG...talk about an ID10T error...I think maybe I spent too much time looking at it to see the obvious! :s

Thanks for pointing it out 🙂

I have a function that may help you...of course, you'd have to use dynamic SQL (which has it's own caveats)

It can be used nicely to return a set of values...

Thanks for the reply Craig. This only shows the execution times and steps for everything "after" the build process completes...which runs exceptionally quick (< .5 secs)

It's the actual build...

(from MSDN)

TRY…CATCH constructs will not fire:

1. Warnings or informational messages that have a severity of 10 or lower.

2. Errors that have a severity of 20 or higher that stop the...

Lynn, sorry I missed that request. The expected result would be an integer value in the prevodometer column for each record in the table.

I don't fully understand why they...

Sorry! Yes I guess that would help 🙂

CREATE FUNCTION [dbo].[fx_GetLastOdometer]

(@date varchar(40)

,@pan VARCHAR(32)

,@tranid int)

RETURNS int

AS

BEGIN

DECLARE @Odometer int

SET @Odometer = (

SELECT TOP 1 odometer

FROM dbo.[Mileage_Table] WITH(INDEX(idx_TranTime))

WHERE tranid <> @tranid

AND pan=@pan

AND...

Done, thanks for the heads up

http://www.sqlservercentral.com/Forums/Topic1048204-145-1.aspx

If I wanted to calculate the average run time for a given SQL Agent job over the past month...knowing that the run_duration column in sysjobshistory is represent as 33848, meaning...

How would you go about adding actual time fields together?

For instance, you have SQL Agent Job run times as follows:

HH:MM:SS

03:58:19

04:18:42

03:14:09

11:31:10 (which would mean 11 hours, 31 minutes, and...

Perhaps I am missing something but this stored-procedure only tells you historically the last time a SQL Agent job started and finished, it does not tell you the start time...

Found it!

Turns out that the software install is user specific and must be individually licensed by each user on the server: Simple installing it as an administrator and registering it...

Again, I can run it from our production box just fine as is (and is SQL 2005), but not from the new box which is SQL 2008.

With the reporting model...

Here are the results:

(1 row(s) affected)

ID TheOutput

----------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

1 NULL

(1 row(s) affected)

Thanks so much for such a detailed response, unfortunately that's not the issue here. Setting up a valid proxy account from AD on each of my DB servers is...

Is LocalServer the instance? If so you cannot easily rename the SQL instance after it has been installed...and it's not reccomended either

However, I did read an article once that...