Thank you, I'll be spending the rest of the afternoon studying this solution.

For the example the expected result set could be as simple as 'false', that is, each date in the date range for the 1st record in Table A cannot be...

Table A Data: 
Id: 1,  Name: Ted,  Start Date: 01/01/2017,  End Date: 12/31/2017

Table B Data:
Id: 1,  Date1: 01/01/2017, Date2: 01/15/2017
Id: 1,  Date1: 02/01/2017,...

BTW, I've found the back and forth in this thread to be valuable.
It has been my opinion for quite some time that the only way to really learn something...

I'm a little skeptical of the concerns regarding the AD going down.  In our environment, if that happened nobody would be able to use their workstations and they wouldn't be...

Thanks for the replies.

The only reason we don't have better practices is because the tech companies earn a great deal of money by constantly changing things. New languages, new IDEs, new frameworks,...

Okay, if I've followed this so far......

1: I should not put a clustered index on my ID field (uniqueidentifier) because it is probably causing a ridiculous number of page splits....

Yes - clustered indexes are good for range searches, but you need to weigh all of the attributes and consequences. As of right now - you have yet to...

FYI: Range searches never happen on these IDs.

Thank you for the response.

A couple of follow up questions, if you don't mind.

1: Why should each table have a clustered index?

2: I could move the clustered index off the...