Assume that you use temporary tables across multiple scopes, you may notice Error 213 or access violation in SQL Server 2019 if you modify the temporary table schema after the initial creation.

Examples of using temporary table in multiple scopes include the following:

  • You create a temporary table in one frame but access it in another frame.

  • You create a temporary table on TSQL batch but access from another TSQL batch.


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


This issue is fixed in the following cumulative update for SQL Server:

About cumulative updates for 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. Check out the latest cumulative updates for SQL Server:


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?

Thank you for your feedback!