I think you'll only get problems if your code uses features that are deprecated in the source version of SQL and have been discontinued in the version on the target...

Hah.  I was just working through this myself.

This seems to work, but using a table variable rather than your temporary table, Thom A.

DECLARE @DataTable...

Yes, that makes sense; however, you can look at the msdb.dbo.sysjobhistory table for the results of the individual steps; combine that with the run-time information from

When setting up the SQL Server scheduled jobs, what you could do is add a final step to each one along the lines of:

declare @JobName varchar(100)

Sounds like an ANSI_NULLS setting thing...  Some sample code:

DECLARE @ClosedStuff TABLE (InspectionClosed DATE NULL);
INSERT INTO @ClosedStuff
VALUES (NULL),(NULL),('19000101'),(GETDATE())

SELECT * FROM @ClosedStuff