FIX: "ADD PERIOD FOR SYSTEM_TIME failed" error when you add period columns to a memory-optimized table in SQL Server 2016

Applies to: SQL Server 2016 Enterprise CoreSQL Server 2016 EnterpriseSQL Server 2016 Developer


Assume that you use In-Memory OLTP in Microsoft SQL Server 2016. In this scenario, you use ALTER TABLE and ADD PERIOD FOR SYSTEM_TIME statements to add period columns that have appropriate default values together with corresponding system-time period to a memory-optimized table. If the table is not empty, you receive an error message that resembles the following:

Msg 13575, Level 16, State 0
ADD PERIOD FOR SYSTEM_TIME failed because table 'TableName' contains records where end of period is not equal to MAX date time.


This fix is included in the following updates:


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology Microsoft uses to describe software updates.