Symptoms

Assume that you run Microsoft SQL Server 2017 or 2016 in a virtualization environment, such as VMWare, in which hot-add CPU and memory functionality are enabled. In this situation, you notice that the SQL Server process terminates unexpectedly and generates an access violation exception in the error log. 

Cause

The exception occurs when SQL Server tries to promote the latch to super latch for database pages that are frequently used.

Status

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

Resolution

Cumulative Update Information

This issue is fixed in the following 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:

Service Pack Information for SQL Server 2016

This problem is fixed in the following service pack for SQL Server:

Service packs are cumulative. Each new service pack contains all the fixes that are in previous service packs, together with any new fixes. We recommend that you apply the latest service pack and the latest cumulative update for that service pack. You do not have to install a previous service pack before you install the latest service pack. Use Table 1 in the following article to find more information about the latest service pack and latest cumulative update.

Determine the version, edition, and update level of SQL Server and its components

More information

For more information about the best practices to be followed for SQL Server configurations in a virtualization environment, see Best practices for SQL Server configurations on VMware.

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!

×