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)
SQL Server 2017 Developer on Windows
SQL Server 2017 Enterprise Core on Windows
SQL Server 2017 Enterprise on Windows
SQL Server 2017 Standard on Windows
SQL Server 2019 on Windows
build lower than 15.0.4013.40
15.0.4013.40
When you process partitions that already have data in Microsoft SQL Server, you may notice that the memory that's expanded from the processing commands does not get released after the processing is completed. In addition, the more processing commands you run, the more the memory grows until there's no more available memory.
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 2 for SQL Server 2019 Cumulative Update 19 for SQL Server 2017 Cumulative Update 11 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 2019 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.