• SQL 2012 makes pretty short work of this type of problem:

    WITH PartitionedSchedules AS

    (

    SELECT ScheduleID, PersonID, startDate, durationDays

    ,CalculatedEndDate=DATEADD(day, durationDays, startDate)

    ,row2startDate=LEAD(startDate, 1) OVER (PARTITION BY PersonID ORDER BY startDate)

    FROM Schedules

    )

    SELECT ScheduleID, PersonID, startDate, durationDays, CalculatedEndDate

    ,row2startDate

    ,datedifference

    ,analysis=CASE SIGN(datedifference)

    WHEN 0 THEN 'contiguous'

    WHEN 1 THEN CAST(ABS(datedifference) AS VARCHAR) + ' days overlap'

    ELSE CAST(ABS(datedifference) AS VARCHAR) + ' days gap'

    END

    FROM PartitionedSchedules a

    CROSS APPLY

    (

    SELECT DATEDIFF(day, row2startDate, CalculatedEndDate)

    ) b (datedifference)

    WHERE datedifference IS NOT NULL;

    No more need for a self-join.


    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    My thought question: Have you ever been told that your query runs too fast?

    My advice:
    INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
    The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.

    Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
    Since random numbers are too important to be left to chance, let's generate some![/url]
    Learn to understand recursive CTEs by example.[/url]
    [url url=http://www.sqlservercentral.com/articles/St