Temporal Tables in SQL Server and Azure SQL Database

Temporal Tables in SQL Server and Azure SQL Database

Temporal Tables in SQL Server and Azure SQL Database

Temporal tables in SQL Server 2016 and later as well as in Azure SQL Database is a new type of user table which was was introduced in ISO/ANSI SQL 2011. Read on to learn more temporal tables and see a comprehensive example that uses them.

 

What are Temporal Tables in SQL Server and Azure SQL Database?

Temporal tables keep a full history of data changes (based on UTC time) by using a pair of current-historical tables. These tables has the same structure.

The period of validity for every row is managed by the system (i.e. Database Engine) by using two explicitly-defined columns of the DateTime2 datatype.

 

Example with Temporal Tables (T-SQL)

Below you can find an example of a user table’s definition that has system versioning enabled:

--Create table along with specifying its historical table
CREATE TABLE dbo.Students2
(
  studentID INT NOT NULL IDENTITY(1,1) CONSTRAINT PK_Students PRIMARY KEY,
  studentName VARCHAR(150) NOT NULL,
  studentAddress VARCHAR(150) NOT NULL,
  regDate DATE NOT NULL,
  SysStartTime DATETIME2 GENERATED ALWAYS AS ROW START HIDDEN NOT NULL,
  SysEndTime DATETIME2 GENERATED ALWAYS AS ROW END HIDDEN NOT NULL,
  PERIOD FOR SYSTEM_TIME (SysStartTime, SysEndTime)
)
WITH (SYSTEM_VERSIONING = ON (HISTORY_TABLE = dbo.Students2History));
GO

 

The above DDL will create two tables: (i) Students2, and (ii) Students2History.

In the “dbo.Students2” table, the user needs to populate only the first 4 columns (studentID, studentName, studentAddress and regDate). Note: In this case “studentID” will be populated automatically too because it is an identity column. The rest of the columns will be maintained automatically by SQL Server’s Database Engine. Table “dbo.Students2History” will be populated fully automatically by the Database Engine.

In the below screenshot we can see both tables:

Temporal Tables in SQL Server - Article on SQLNetHub
Figure 1: Pair of Current-Historical Table

Let’s check both tables for any contents:

Temporal Tables in SQL Server - Article on SQLNetHub
Figure 2: Table Contents.

 

Now, let’s insert some data in the “dbo.Students2” table:

--Insert initial data
INSERT INTO dbo.Students2
        ( studentName ,
          studentAddress ,
          regDate 
        )
VALUES  ( 'John Adams', 
          'Address 1', 
          GETDATE() 
        );
GO

 

Let’s check again both tables for any contents:

Temporal Tables in SQL Server - Article on SQLNetHub
Figure 3: Table Contents After Insert.

As you can see, the “dbo.Students2” table was populated with data.

The “dbo.Students2History” table was not populated with any data because system versioning works only in case of an update operation against one or more rows.

That being said, let’s try to update the row:

--Now let's update a record
UPDATE dbo.Students2
SET studentAddress='Address 1 Update'
WHERE studentID=1;
GO

 

Let’s check again the table contents:

Temporal Tables in SQL Server - Article on SQLNetHub
Figure 4: Table Contents After Update Operation.

Now you can see that the table “Students2History” contains the original values for row with studentID=1 just before the update operation took place.

Let’s update the same record again:

--Update the same record
UPDATE dbo.Students2
SET studentAddress='Address 1 Update 2'
WHERE studentID=1;
GO

 

Let’s check the table contents:

Temporal Tables in SQL Server - Article on SQLNetHub
Figure 5: Table Contents After Second Update.

As you can see, the table “Students2History” contains also the “new” original value for row with studentID=1 just before the new update operation took place. So in total, the historical table contains the rows for studentID=1 just before the two update operations took place. The validity of each row can be determined from the “SysStartTime” and “SysEndTime” values.

 

Conclusion

This article was a simple example of using temporal tables in SQL Server 2016. I consider temporal tables one of the top new features in SQL Server 2016 as they have to offer significant functionality.
Some benefits of using temporal tables:
  • Auditing all data changes (i.e. for data forensics)
  • Data reconstruction/recovery
  • Trends monitoring over time

 

 

Did you find this article useful and interesting? Feel free to leave your comment!

If you enjoy my SQL Server administration tips and articles, I have something special just for you. It is one of my eBooksand it is called “Administering SQL Server“. Check it out!

Subscribe to our newsletter and stay up to date with our latest articles on SQL Server and related technologies!

Check out our latest software releases! All our software tools have free trial versions to download.

 

Rate this article: 1 Star2 Stars3 Stars4 Stars5 Stars (1 votes, average: 5.00 out of 5)

Loading...

Reference: SQLNetHub.com (https://www.sqlnethub.com)

© SQLNetHub

Artemakis Artemiou
Artemakis Artemiou is a Senior SQL Server Architect, Author, and a 9 Times Microsoft Data Platform MVP (2009-2018). He has over 15 years of experience in the IT industry in various roles. Artemakis is the founder of SQLNetHub and TechHowTos.com. Artemakis is the creator of the well-known software tools Snippets Generator and DBA Security Advisor. Also, he is the author of many eBooks on SQL Server. Artemakis currently serves as the President of the Cyprus .NET User Group (CDNUG) and the International .NET Association Country Leader for Cyprus (INETA). Artemakis's official website can be found at aartemiou.com.