Have you ever had to create databases using Temporal Database design Patterns using any current day Relational Database?
Doesn't SQL Server now have the horse power to handle advanced database designs?
How about adding Temporal capability to SQL Server to either the Engine or as an Add On the way Analysis Services, Reporting Services, etc.
The classic example is to have a contact database that is able to track the changes to last names for married women. You have a contact table, but you also need a table to track the last names of the women and it's effective date. Can't this be transparent or utilize SQL 3's temporal standards?