IntervalMatch won't work on your tables as they are - you'll need day level data.
To resolve this, I'd create a calendar table. Then I'd create a link table using Intervalmatch to match your Plans to the Calendar. Finally I'd use an Intervalmatch on this to join to the Features.
Hope this makes sense.
Thank you for the quick response. I think I was trying to over complicate how this would be built out. It did seem like since there were the two date ranges it needed the partition option but really it's a single table with a different type of record. Type = Plan or Feature. With the interval match on the Calendar table I can pick any date and it will pull the single Plan and any Features active at that time.
The only thing I had to do as I could not make this work was place a far out date for any currently active Plan or Feature. It works but seems like its not the best solution.
Example: Plan4 added future PlanEndDt
PlanSKU PlanStartDt PlanEndDt Plan1 1/11/2013 1/14/2013 Plan2 1/15/2013 12/15/2013 Plan3 12/15/2013 5/15/2015 Plan4 5/15/2015 12/31/2016