data-konzept

'If you’re new to SQL Server, you might have heard or read some of the above statements. If you’ve never used a trace flag, you might wonder why you might need one, and how you would know if you did need it. SQL Server trace flags are used to change the behavior of the engine in some way. A trace flag is ideally used for improvement, but there can be situations where a trace flag doesn’t provide the intended benefit. In some cases, it can adversely affect the problem you’re trying to fix, or create a different issue. As such, trace flags in SQL Server are something to use with caution. The number one recommendation I always make when someone asks about using a trace flag is to test it, ideally in an identical or comparable situation.  This isn’t always possible, which is why there’s always a slight risk with trace flags. There are only three (3) trace flags that we at SQLskills recommend, by default, for a SQL Server installation:​

• 1118 (for versions prior to SQL Server 2016)
• 3023 (for versions prior to SQL Server 2014)
• 3226'...

https://www.sqlskills.com/blogs/erin/sqlskills-101-trace-flags/