Symptoms

With the introduction of contained databases in SQL Server, the database engine always performs a containment check before executing stored procedures. On high-end computers with multiple cores, this check may cause a decrease in performance because of internal spinlock contention, occasionally causing "non-yielding scheduler" errors.

Resolution

This problem was first 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:

Latest cumulative update for SQL Server 2014 (SP1/SP2)

Latest cumulative update for SQL Server 2016 

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 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!

×