Understanding Temporal Tables in SQL Server

Temporal tables are a powerful feature introduced in SQL Server 2016 that provides a built-in mechanism for capturing and querying historical data. They enable you to keep track of all changes made to the data in a table, which can be crucial for auditing, compliance, and data analysis. This article will delve into what temporal tables are, how they work, and how to implement them effectively.

What are Temporal Tables?

Temporal tables, also known as system-versioned tables, automatically maintain a full history of data changes. They consist of two components:

  1. Current Table: Stores the current data.
  2. History Table: Automatically stores the historical versions of data.

When a row in the current table is updated or deleted, SQL Server moves the previous version of the row to the history table. This allows you to query historical data at any point in time.

Key Features of Temporal Tables

  1. Automated Data Management: Automatically manages the movement of historical data to the history table.
  2. Point-in-Time Analysis: Allows querying data as it appeared at any specific point in time.
  3. Auditing and Compliance: Provides an audit trail of changes for regulatory compliance.
  4. Data Recovery: Enables recovery of data to a previous state without complex restore operations.

Creating Temporal Tables

Creating a temporal table involves specifying system versioning during table creation. Here’s a step-by-step guide.

  1. Define the Current Table: Include period columns for system start and end times.
    CREATE TABLE Employees
        EmployeeID INT PRIMARY KEY,
        Name NVARCHAR(100),
        Position NVARCHAR(100),
        Salary DECIMAL(18, 2),
        PERIOD FOR SYSTEM_TIME (SysStartTime, SysEndTime)
    WITH (SYSTEM_VERSIONING = ON (HISTORY_TABLE = dbo.EmployeesHistory));

In this example,

  • SysStartTime and SysEndTime are the system period columns.
  • PERIOD FOR SYSTEM_TIME defines the period of system time.

Automatically Manage History Table

SQL Server creates and manages the history table.

Querying Temporal Tables

Temporal tables allow you to query historical data using the FOR SYSTEM_TIME clause.

SELECT * FROM Employees FOR SYSTEM_TIME BETWEEN '2023-01-01T00:00:00' AND '2023-01-01T23:59:59';
  1. Retrieve Current Data
    SELECT * FROM Employees;
  2. Retrieve Data at a Specific Point in Time
    SELECT * FROM Employees FOR SYSTEM_TIME AS OF '2023-01-01T12:00:00';
  3. Retrieve Data Over a Time Range
    SELECT * FROM Employees FOR SYSTEM_TIME BETWEEN '2023-01-01T00:00:00' AND '2023-01-01T23:59:59';
  4. Retrieve All Historical Data

Managing Temporal Tables

  1. Turn Off System Versioning: You can turn off system versioning to make schema changes or manage data manually.
  2. Re-enable System Versioning
    ALTER TABLE Employees SET (SYSTEM_VERSIONING = ON (HISTORY_TABLE = dbo.EmployeesHistory));
  3. Cleanup Old Data: To manage the size of the history table, you can periodically archive or clean up old data:
    DELETE FROM EmployeesHistory WHERE SysEndTime < '2022-01-01T00:00:00';

Best Practices

  1. Indexing: Ensure proper indexing on period columns to optimize query performance.
  2. Data Retention Policies: Implement data retention policies to manage the growth of the history table.
  3. Security: Secure both current and history tables to prevent unauthorized access to sensitive historical data.


Temporal tables in SQL Server offer a robust solution for managing historical data, providing significant benefits for auditing, compliance, and point-in-time analysis. By automatically capturing and storing historical versions of data, they simplify the process of tracking changes over time. With the ability to query data as it existed at any point in time, temporal tables enhance the capabilities of SQL Server for modern data management needs. Implementing temporal tables involves a straightforward setup, and with best practices in place, they can significantly improve your data management strategy.

Similar Articles