I got a strange value for only a couple of rows in my sysjobhistory table for the run_duration column.
The job kicked off at 1:54am on 11/1/15. This is the day we changed from daylight to standard time.
So the job thinks it ended before it began, hence the negative duration. Problem solved! Had me perplexed for a few days until I checked the start date and time.
- Paul Paiva
- Paul has 18 years experience with Microsoft SQL Server. He has worked in the roles of production DBA, database developer, database architect, applications developer, business intelligence and data warehouse developer, and instructor for students aspiring for MCDBA certification. He has performed numerous data migrations and supported large databases (3 Terabyte, 1+ billion rows) with high transactions. He is a member of PASS, blogs about lessons learned from a developer’s approach to SQL Server administration, and has been the president of the Boulder SQL Server Users’ Group from January 2009 to present.