April 23, 2013 at 7:38 am
Excellent!!!
Rudy
April 23, 2013 at 12:16 pm
Lots of errors on this list. For instance, 3604 is used for all kinds of output from undocumented DBCC commands. Be careful when playing with these.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
April 23, 2013 at 1:11 pm
Anybody have any experience with 3499, The few pages I've found on google say this is to change the default behavior of a mirror database. (The mirror would treat the transaction log more like the principal vice hardening every transaction.) Just curious if anyone is using this or has it working. I've tested but saw no change whatsoever. Wondering if this (undocumented) flag was quietly deprecated in a service pack.
May 29, 2013 at 12:03 am
Next update coming on 05 Jul 2013.
July 5, 2013 at 1:00 pm
Nicely done!
October 17, 2013 at 7:24 am
Please add trace flag 8605, according to Paul White's blog: http://sqlblog.com/blogs/paul_white/archive/2012/04/28/query-optimizer-deep-dive-part-1.aspx
Thanks,
Jim
October 17, 2013 at 7:27 am
Thanks I'll add it up in the next update.
June 11, 2014 at 4:02 pm
It's been a while, so here's a few more:
Trace Flag: 9481
Purpose: Use when running SQL Server 2014 with the default database compatibility level 120. Trace flag 9481 forces the query optimizer to use version 70 (the SQL Server 2012 version) of the cardinality estimator when creating the query plan.
KB Article: http://support.microsoft.com/kb/2801413
First Added: SQL 2014
Versions: SQL 2014
Trace Flag: 2312
Purpose: Use when running SQL Server 2014 with database compatibility level 110, which is the compatibility level for SQL Server 2012. Trace flag 2312 forces the query optimizer to use version 120 (the SQL Server 2014 version) of the cardinality estimator when creating the query plan.
KB Article: http://support.microsoft.com/kb/2801413
First Added: SQL 2014
Versions: SQL 2014
Trace Flag: 101, 102
Purpose: Troubleshoot merge replication performance issues
KB Article: http://support.microsoft.com/kb/2892633
First Added: SQL 2005
Versions: SQL 2005, SQL 2008, SQL 2008 R2, SQL 2012
Trace Flag: 849
Purpose: SQL may display memory corruption and recovery errors
KB Article: http://support.microsoft.com/kb/2967651
First Added: SQL 2005
Versions: SQL 2005, SQL 2008, SQL 2008 R2, SQL 2012, SQL 2014
Trace Flag: 2453
Purpose: Allows the query optimizer to use information about the number of rows inserted into a table variable in order to select more efficient query plan
KB Article: http://support.microsoft.com/kb/2958429
First Added: SQL 2012 SP2
Versions: SQL 2012 SP2
June 11, 2014 at 8:16 pm
Thanks for your contribution RON, I'll update these & a few more in the July release.
December 6, 2016 at 12:58 am
More detailed and modern version here: https://github.com/ktaranov/sqlserver-kit/blob/master/SQL%20Server%20Trace%20Flag.md
Viewing 10 posts - 61 through 69 (of 69 total)
You must be logged in to reply to this topic. Login to reply