Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 13359752
KB4541132 - Improvement: Size and retention policy are increased in default XEvent trace system_health in SQL Server 2016, 2017 and 2019 - Microsoft Support
Last update date:
9/16/2021
Affected products:
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 2019 on Linux
SQL Server 2019 on Windows
SQL Server 2017 on Linux
SQL Server 2017 on Windows
SQL Server 2017 Developer Linux
SQL Server 2017 Enterprise Core on Linux
SQL Server 2017 Enterprise on Linux
SQL Server 2017 Standard on Linux
Affected releases:
build lower than 15.0.4023.6
Fixed releases:
15.0.4023.6
Description:
Improvement
The current definition for the system_health XEvent session has a maximum file size of 5 megabytes (MB) and maximum of 4 files for a total maximum of 20 MB of system_health XEvent data. On systems that have a lot of activity, you can roll over this limitation very quickly and miss important information in the event of a problem that affects the system. In order to keep more troubleshooting data available on the system, the default file size is changed in this update from 5 MB to 100 MB, and the default number of files is changed from 4 to 10, for a total maximum of 1 GB of system_health XEvent data. If the definition of the system_health session was already modified from the default values, this improvement will not overwrite the existing settings. Additionally, you can change the system_health session configuration manually by using the following Transact-SQL script: ALTER EVENT SESSION [system_health] ON SERVER DROP TARGET package0.event_file ALTER EVENT SESSION [system_health] ON SERVER ADD TARGET package0.event_file ( SET filename=N'system_health.xel', max_file_size=(100), max_rollover_files=(10) )
Resolution
This improvement is included in the following cumulative updates for SQL Server: Cumulative Update 3 for SQL Server 2019 Cumulative Update 20 for SQL Server 2017 Cumulative Update 12 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
Service pack information for SQL Server 2016
This issue is fixed in the following service pack for SQL Server: Service Pack 3 for SQL Server 2016
References
Learn about the terminology that Microsoft uses to describe software updates.
