Welcome to the Lounge

public static class ExtendTimeSpan
{
    public static TimeSpan ParseFromFormattedInt(int value)
    {
        int hours = Math.DivRem(value, 10000, out value);
        int minutes = Math.DivRem(value, 100, out value);
        int seconds = value + minutes * 60 + hours * 3600;
        return TimeSpan.FromSeconds(seconds);
    }
 
    public static TimeSpan ParseFromFormattedInt(this TimeSpan span, int value)
    {
        return ParseFromFormattedInt(value);
    }
}

SELECT 
    TIMEFROMPARTS(active_end_time / 10000, (active_end_time / 100) % 100, active_end_time % 100, 0, 0)
FROM
    msdb.dbo.sysschedules
;

Richard Deeming wrote:

Or, in SQL (2012 or later):

int year = Math.DivRem(value, 10000, out value);
int month = Math.DivRem(value, 100, out value);
int day = value;
return new DateTime(year, month, day);

TimeSpan span = TimeSpan.FromSeconds(1); 

OriginalGriff wrote:

It's silly, but I see the logic

OriginalGriff wrote:

"Number of seconds since midnight" is a better solution except for the human readable bit:

Mike Winiberg wrote:

You are right, of course. I don't know how things were/are stored internally in SQL Server, but even in 16 bit stuff you could usually store 32bit INTs, which is still smaller than the 48bits needed for "235959".

Quote:

The Metric Leisure Week will be composed of three days. Yes, only three days. Monday, Tuesday and Wednesday will become one day known as Mwensday or in decabet: Mwen. Thursday, Friday and Saturday will become Saturthurs, or in decabet: Turth. And Sunday, our traditional day of rest, will remain Sunday. Three days: Mwen, Thurth and Sunday.

OriginalGriff wrote:

The silliness if you think about it is having 60 seconds to the minute, 60 minutes to the hour, 24 hours to the day - instead of using a minute that was about 50% longer than the current one, made up of 100 (slightly longer) seconds, and having 1000 new-minutes in a day.