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?
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? Read More