Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««34567

SQL Server Trace Flags Expand / Collapse
Author
Message
Posted Tuesday, April 23, 2013 7:38 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 7:01 AM
Points: 315, Visits: 1,115
Excellent!!!


Post #1445423
Posted Tuesday, April 23, 2013 12:16 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Thursday, September 11, 2014 3:05 AM
Points: 2,039, Visits: 1,665
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
Post #1445623
Posted Tuesday, April 23, 2013 1:11 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, June 10, 2014 5:12 AM
Points: 159, Visits: 178
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.
Post #1445658
Posted Wednesday, May 29, 2013 12:03 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Sunday, September 28, 2014 8:10 PM
Points: 267, Visits: 867
Next update coming on 05 Jul 2013.
Post #1457588
Posted Friday, July 5, 2013 1:00 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Wednesday, July 9, 2014 1:52 PM
Points: 352, Visits: 121
Nicely done!
Post #1470845
Posted Thursday, October 17, 2013 7:24 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, September 16, 2014 3:39 PM
Points: 3, Visits: 99
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
Post #1505696
Posted Thursday, October 17, 2013 7:27 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Sunday, September 28, 2014 8:10 PM
Points: 267, Visits: 867
Thanks I'll add it up in the next update.
Post #1505698
Posted Wednesday, June 11, 2014 4:02 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: 2 days ago @ 7:59 AM
Points: 70, Visits: 503
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


Post #1579841
Posted Wednesday, June 11, 2014 8:16 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Sunday, September 28, 2014 8:10 PM
Points: 267, Visits: 867
Thanks for your contribution RON, I'll update these & a few more in the July release.
Post #1579868
« Prev Topic | Next Topic »

Add to briefcase «««34567

Permissions Expand / Collapse