This is a decent workaround for something SQL Server doesn't seem to adequately support (afaik): temporal awareness
Not to plug another rdbms, but the one starting with "p" has gone a long ways towards implementing duration constraints for overlaps and other types of non-/partial-/extra-equi comparisons (or "Exclusion Constraints", as they're referred to).
Not only that, the PERIOD data type has been generalized to include distance or most any other type of continuous range (cf. "range types").
Using a Start and End column for a timespan has never made much sense to me. It's one datum, not two disjunct attributes relatable only by their row index.
It would be nice to see SQL Server deal seriously with this type of data.
My 2 cantakerous cents :satisfied: