I had never heard of TF 2371 until seeing your post. From looking at http://blogs.msdn.com/b/saponsqlserver/archive/2011/09/07/changes-to-automatic-update-statistics-in-sql-server-traceflag-2371.aspx
it seems to me that TF 2371 would be useful in the following situations:
a) You have some large tables of over 1 million rows
b) The indexes relied on by your queries contain columns whose value is time-dependant (in most situations this means dates, but it could be a derived column such as partition number that is dependant on a date value)
Because TF 2371 triggers more frequent statistics updates, it means the queries that use date-dependant indexes are more likely to get the optimum plan.
Some sites do a weekly update of indexes on all tables, partly to overcome the long lag between automatic updates using the standard 20% change figure. For these people TF 2371 could become an alternative to a weekly stats update.
If you do use TF 2371 I suggest you also turn on asynchronous stats update, as this will avoid a query being stalled while the stats update completes. WARNING: Async stats updates causes a memory leak in some old fix levels - check you have the fix for this problem installed.
Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005. 14 Mar 2017
: now over 40,000 downloads.Disclaimer: All information provided is a personal opinion that may not match reality.Quote: When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist. - Archbishop Hélder Câmara