Comments on: Making date and time sense from the SQL Server Agent job history table http://craign.net/2009/11/26/making-date-and-time-sense-from-the-sql-server-agent-job-history-table/ Thoughts about life, the universe and everything else. Wed, 01 Sep 2010 13:17:14 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Gail http://craign.net/2009/11/26/making-date-and-time-sense-from-the-sql-server-agent-job-history-table/comment-page-1/#comment-12064 Gail Fri, 27 Nov 2009 14:16:15 +0000 http://craign.net/2009/11/26/making-date-and-time-sense-from-the-sql-server-agent-job-history-table/#comment-12064 It's been like this for many versions, but that's no excuse. There are far better ways to express times, even using a string, than it's using. The duration is stored in the same way. Have fun working out how long a job ran for... Frankly, MSDB is a wonderful example of a terribly designed database. Don't even get me started on sysjobschedules. I had three UDFs that I used to use to turn the data into something actually usable. It’s been like this for many versions, but that’s no excuse. There are far better ways to express times, even using a string, than it’s using. The duration is stored in the same way. Have fun working out how long a job ran for…

Frankly, MSDB is a wonderful example of a terribly designed database. Don’t even get me started on sysjobschedules.

I had three UDFs that I used to use to turn the data into something actually usable.

]]> By: Craig Nicholson http://craign.net/2009/11/26/making-date-and-time-sense-from-the-sql-server-agent-job-history-table/comment-page-1/#comment-12050 Craig Nicholson Thu, 26 Nov 2009 19:37:36 +0000 http://craign.net/2009/11/26/making-date-and-time-sense-from-the-sql-server-agent-job-history-table/#comment-12050 Well I suppose its a legacy design issue from the days of Sybase or something like that. Perhaps they never had a DATETIME data type then the next best would be two 32-bit integers. I would have thought though that they would have put a new table down and created a view for backwards compatibility or something. They seem to have done it for other tables. Well I suppose its a legacy design issue from the days of Sybase or something like that. Perhaps they never had a DATETIME data type then the next best would be two 32-bit integers. I would have thought though that they would have put a new table down and created a view for backwards compatibility or something. They seem to have done it for other tables.

]]> By: Brady Kelly http://craign.net/2009/11/26/making-date-and-time-sense-from-the-sql-server-agent-job-history-table/comment-page-1/#comment-12049 Brady Kelly Thu, 26 Nov 2009 19:35:04 +0000 http://craign.net/2009/11/26/making-date-and-time-sense-from-the-sql-server-agent-job-history-table/#comment-12049 What were they thinking? The mind boggles. This is even worse than storing the date and time as strings, as it's one conversion further from the truth. What were they thinking? The mind boggles. This is even worse than storing the date and time as strings, as it’s one conversion further from the truth.

]]>