Symptoms

In SQL Server 2016, on a memory-optimized table, most ALTER TABLE scenarios now run in parallel and result in an optimization of writes to the transaction log. However, alter column operations on a large memory-optimized table that run in parallel may result in data loss. 

NoteALTER TABLE operations run single-threaded and are not affected by this issue.

Resolution

The issue was first fixed in the following cumulative update of SQL Server:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install the latest cumulative updates for SQL Server:


Workaround

To work around this issue, turn off the log-optimized for the alter operations by enabling trace flag 9909. 

To enable trace flag 9909, add the -T9909 startup parameter. Or, you can use the dbcc traceon(9909) statement for a specific session.

Status

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

References

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×