Forum Discussion
SQL Server Trace Flag 5013
We have been advised to apply Trace Flag 5013 to our Production servers running SQL Server 2017 or above. My issue here is that this flag undocumented, so we are not able to verify exactly what it does. It does make our third-party product more stable, but we don’t know if we’d be introducing any other undesired effects onto our estates. I’d like to ask if anyone out there has had any experience with this flag?
Crabbers , see Database Engine events and errors (5000 to 5999) - SQL Server | Microsoft Learn => 5013 = "The master and model databases cannot have files added to them. ALTER DATABASE was aborted."
If it's neccessary to activate such a trace flag for the app to run stable, then the app is more then buggy.
And when you post the same across all forum, please add a reference to.
SQL Server Trace Flag 5013 - Database Administrators Stack Exchange
