Trace flag 8048. Feb 28, 2022 · This means that trace flag -T8048 is no longer valid or needed on SQL Server 2016 because the design is such that SQL Server dynamically adjusts to CMemThread wait activities in order to optimize performance. Moderate testing I ran tests on some fairly large tables. Performance fixes that are included in a cumulative update Show 3 more. Dec 18, 2019 · NOTE: There are a few additional trace flags, that I haven’t use, that have been changed, about NUMA and one about VAS fragmentation with page allocation errors, to defaulted behaviors 8048, 8075, 8079 you can read about at the link above. Jun 12, 2025 · In this article Apply the recommended updates and improve the performance of SQL Server 2014 and SQL Server 2012 Table 1. General considerations and best practices for improving performance of your instance of SQL Server Table 3. Because trace flags set using the -T command-line option automatically apply to all There is a good CSS post about CMEMTHREAD waits and debugging them here, which explains how the trace flag 8048 may help alleviate the issue if the memory object is one that is currently partitioned by NUMA node. This ensures the trace flag remains active after a server restart. Mar 3, 2016 · As of 02/23/2016, it sounds like Trace Flag 8048 is also enabled by default in 2016. I tried to run them on tables from 100 million to 1 billion rows, but I blew out the data drive of our AWS instance. erjehd rdwa7kn exfcin6 7qvd cilj utae 4ok igtjft btnk gi09