BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
6/2/2022
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
build lower than 14.0.3238.1
14.0.3238.1
Assume that you use Microsoft SQL Server 2016 or 2017. When you run some queries that use batch-mode hash join and/or batch-mode sort, you may notice these queries can spill a lot of data because of memory pressure, and a "Non-yielding Scheduler" condition occurs.
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 updates for SQL Server: Cumulative Update 17 for SQL Server 2017 Cumulative Update 8 for SQL Server 2016 SP2 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 2017 Latest cumulative update for SQL Server 2016
Learn about the terminology that Microsoft uses to describe software updates.