OPERATIONAL DEFECT DATABASE
...
...
Assume that you have very large database with thousands of tables and millions of columns in Microsoft SQL Server. When you run the statement UPDATE STATISTICS to generate a maintenance plan, you may notice that the UPDATE STATISTICS takes a very long time (approximately 24-48 hours) to prepare metadata for large databases.
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 18 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.
The included affected builds are considered potentially affected, based on their release chronology relative to the identified fix.
Click on a version to see all relevant bugs
Microsoft SQL Server Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
