Packt+ | Advance your knowledge in tech

You're reading from SQL Server 2017 Developer???s Guide A professional guide to designing and developing enterprise database applications

Product type Paperback

Published in Mar 2018

Publisher Packt

ISBN-13 9781788476195

Length 816 pages

Edition 1st Edition

Languages

SQL

Tools

SQL Server

Concepts

Database Programming

Authors (3):

Dejan Sarka

Milo≈° Radivojeviƒá

William Durkin

View More author details

Table of Contents (19) Chapters

Preface

1. Introduction to SQL Server 2017 FREE CHAPTER

2. Review of SQL Server Features for Developers

3. SQL Server Tools

4. Transact-SQL and Database Engine Enhancements

5. JSON Support in SQL Server

6. Stretch Database

7. Temporal Tables

8. Tightening Security

9. Query Store

10. Columnstore Indexes

11. Introducing SQL Server In-Memory OLTP

12. In-Memory OLTP Improvements in SQL Server 2017

13. Supporting R in SQL Server

14. Data Exploration and Predictive Modeling with R

15. Introducing Python

16. Graph Database

17. Containers and SQL on Linux

18. Other Books You May Enjoy

Leave a review - let other readers know what you think

System-versioned temporal tables in SQL Server 2017

SQL Server 2016 introduces support for system-versioned temporal tables. Unfortunately, application-time tables are not implemented neither in this version, nor in SQL Server 2017. System-versioned temporal tables bring built-in support for providing information about data stored in the table at any point in time rather than only the data that is correct at the current moment in time. They are implemented according to the specifications in the ANSI SQL:2011 standard with a few extensions.

How temporal tables work in SQL Server 2017

A system-versioned temporal table is implemented in SQL Server 2017 as a pair of tables: the current table containing the actual data, and the history table where only historical entries are stored. There are many limitations for both current and history tables. Here are limitations and considerations that you must take into account for the current table of a system-versioned temporal table: