Introducing temporal tables and adding this functionality to existing tables can significantly increase storage used for data in your system. Since there is no out-of-the-box solution for managing the retention of history tables, if you don't do something, data will remain there forever. This can be painful for storage costs, maintenance, and performance of queries on temporal tables, especially if rows in your current tables are heavily updated.
Performance and storage considerations with temporal tables
Get SQL Server 2017 Developer's Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.