Sybase数据库技术，数据库恢复专家 » trace flag

SQL Server TRACE FLAGS

dbainfo — Thu, 05 Aug 2010 06:16:21 +0000

转自：http://blog.csdn.net/obuntu/archive/2010/06/08/5655494.aspx

谢谢obuntu

flag	Trace Flag Description (underlined are sp_configure’able)
-1	Sets trace flags for all connections. Used only with DBCC TRACEON and TRACEOFF. The setting of the Trace flag -1 is not visible with DBCC TRACESTATUS command, but work without problems.
105	SQL Server 6.5 you can use maximum 16 tables or subqueries in a single select statement. There is no documented way, to avoid this restriction, but you can use undocumented trace flag 105 for this purpose.
106	Disables line number information for syntax errors.
107	Interprets numbers with a decimal point as float instead of decimal.
110	Turns off ANSI select characteristics.
204	A backward compatibility switch that enables non-ansi standard behavior. E.g. previously SQL server ignored trailing blanks in the like statement and allowed queries that contained aggregated functions to have items in the group by clause that were not in the select list.
205	Report when a statistics-dependent stored procedure is being recompiled as a result of AutoStat.
206	Provides backward compatibility for the setuser statement.
208	SET QUOTED IDENTIFIER ON.
237	Tells SQL Server to use correlated sub-queries in Non-ANSI standard backward compatibility mode.
242	Provides backward compatibility for correlated subqueries where non-ANSI-standard results are desired.
243	The behavior of SQL Server is now more consistent because null ability checks are made at run time and a null ability violation results in the command terminating and the batch or transaction process continuing.
244	Disables checking for allowed interim constraint violations. By default, SQL Server checks for and allows interim constraint violations. An interim constraint violation is caused by a change that removes the violation such that the constraint is met, all within a single statement and transaction. SQL Server checks for interim constraint violations for self-referencing DELETE statements, INSERT, and multi-row UPDATE statements. This checking requires more work tables. With this trace flag you can disallow interim constraint violations, thus requiring fewer work tables.
246	Derived or NULL columns must be explicitly named in a select….INTO or create view statement when not done they raise an error. This flag avoids that.
253	Prevents ad-hoc query plans to stay in cache.
257	Will invoke a print algorithm on the XML output before returning it to make the XML result more readable.
260	Prints versioning information about extended stored procedure dynamic-link libraries (DLLs). For more information about __GetXpVersion() , see Creating Extended Stored Procedures . Scope: global or session
262	SQL 7 - Trailing spaces are no longer truncated from literal strings in CASE statements. Used after hotfix 891116
302	Should be used with flag 310 to show the actual join ordering. Prints information about whether the statistics page is used, the actual selectivity (if available), and what SQL Server estimated the physical and logical I/O would be for the indexes.
310	Prints information about join order. Index selection information is also available in a more readable format using SET SHOWPLAN_ALL, as described in the SET statement.
320	Disables join-order heuristics used in ANSI joins. To see join-order heuristics use flag 310. SQL Server uses join-order heuristics to reduce the no’ of permutations when using the best join order.
323	Reports on the use of update statements using UPDATE in place. Shows a detailed description of the various update methods used by SQL Server 6.5.
325	Prints information about the cost of using a non-clustered index or a sort to process an ORDER BY clause.
326	Prints information about the estimated & actual costs of sorts. Instructs the server to use arithmetic averaging when calculating density instead of a geometric weighted average when updating statistics. Useful for building better stats when an index has skew on the leading column. Use only for updating the stats of a table/index with known skewed data.
330	Enables full output when using the SET SHOWPLAN_ALL option, which gives detailed information about joins.
342	Disables the costing of pseudo-merge joins, thus significantly reducing time spent on the parse for certain types of large, multi-table joins. One can also use SET FORCEPLAN ON to disable the costing of pseudo-merge joins because the query is forced to use the order specified in the FROM clause.
345	Increase the accuracy of choice of optimum order when you join 6 or more tables.
506	Enforces SQL-92 standards regarding null values for comparisons between variables and parameters. Any comparison of variables and parameters that contain a NULL always results in a NULL.
610	SQL 10 – Enable the potential for minimal-logging when: · Bulk loading into an empty clustered index, with no nonclustered indexes · Bulk loading into a non-empty heap, with no nonclustered indexes
611	After SQL 9 when turned on, each lock escalation is recorded in the SQL Server error log along with the SQL Server handle number.
652	Disables read ahead for the server.
653	Disables read ahead for the current connection.
661	Disables the ghost record removal process. A ghost record is the result of a delete operation. When you delete a record, the deleted record is kept as a ghost record. Later, the deleted record is purged by the ghost record removal process. When you disable this process, the deleted record is not purged. Therefore, the space that the deleted record consumes is not freed. This behavior affects space consumption and the performance of scan operations. SCOPE : Global. If you turn off this trace flag, the ghost record removal process works correctly.
806	Cause 'DBCC-style' page auditing to be performed whenever a database page is read into the buffer pool. This is useful to catch cases where pages are being corrupted in memory and then written out to disk with a new page checksum. When they're read back in the checksum will look correct, but the page is corrupt (because of the previous memory corruption). This page auditing goes someway to catching this - especially on non-Enterprise Edition systems that don't have the 'checksum sniffer'.
809	SQL 8 – Limits the amount of Lazy Write activity.
815	Enables latch enforcement. SQL Server 8 (with service pack 4) and SQL Server 9 can perform latch enforcement for data pages found in the buffer pool cache. Latch enforcement changes the virtual memory protection state while database page status changes from "clean" to "dirty" ("dirty" means modified through INSERT, UPDATE or DELETE operation). If an attempt is made to modify a data page while latch enforcement is set, it causes an exception and creates a mini-dump in SQL Server installation's LOG directory. Microsoft support can examine the contents of such mini-dump to determine the cause of the exception. In order to modify the data page the connection must first acquire a modification latch. Once the data modification latch is acquired the page protection is changed to read-write. Once the modification latch is released the page protection changes back to read-only.
818	SQL 8 enables in memory ring buffer used to track last 2048 successful write operations.
830	SQL 9 – disable the reporting of CPU Drift errors in the SQL Server errorlog like SQL Server has encountered 2 occurrence(s) of I/O requests taking longer than 15 seconds to complete
834	Causes SQL Server to use Windows large-page allocations for the memory that is allocated for the buffer pool. The page size varies depending on the hardware platform, but the page size may be from 2 MB to 16 MB. Large pages are allocated at startup and are kept throughout the lifetime of the process. Trace flag 834 improves performance by increasing the efficiency of the translation look-aside buffer (TLB) in the CPU. Flag 834 applies only to 64-bit versions of SQL Server. You must have the Lock pages in memory user right to turn on trace flag 834. You can turn on trace flag 834 only at startup. Trace flag 834 may prevent the server from starting if memory is fragmented and if large pages cannot be allocated. Therefore, trace flag 834 is best suited for servers that are dedicated to SQL Server. For more information about large-page support, http://msdn2.microsoft.com/en-us/library/aa366720.aspx (http://msdn2.microsoft.com/en-us/library/aa366720.aspx)
835	SQL 9 & 10. For 64 bit SQL Server. This turns off Lock pages in memory.
836	Causes SQL Server to size the buffer pool at startup based on the value of the max server memory option instead of based on the total physical memory. You can use trace flag 836 to reduce the number of buffer descriptors that are allocated at startup in 32-bit Address Windowing Extensions (AWE) mode. Trace flag 836 applies only to 32-bit versions of SQL Server that have the AWE allocation enabled. You can turn on trace flag 836 only at startup.
845	SQL 9 & 10. For 64 bit SQL Server. This turns on Lock pages in memory.
1117	Grows all data files at once, else it goes in turns.
1118	Switches allocations in tempDB from 1pg at a time (for first 8 pages) to one extent. There is now a cache of temp tables. When a new temp table is created on a cold system it uses the same mechanism as for SQL 8. When it is dropped though, instead of all the pages being deallocated completely, one IAM page & one data page are left allocated, then the temp table is put into a special cache. Subsequent temp table creations will look in the cache to see if they can just grab a pre-created temp table. If so, this avoids accessing the allocation bitmaps completely. The temp table cache isn't huge (32 tables), but this can still lead to a big drop in latch contention in tempdb. http://www.sqlskills.com/BLOGS/PAUL/post/Misconceptions-around-TF-1118.aspx
1180	Forces allocation to use free pages for text or image data and maintain efficiency of storage. 1197 applies only in the case of SQL 7 – SP3. Helpful in case when DBCC SHRINKFILE and SHRINKDATABASE commands may not work because of sparsely populated text, ntext, or image columns
1197
1200	Prints lock information (the process ID and type of lock requested).
1202	Insert blocked lock requests into syslocks.
1204	Returns resources and types of locks participating in a deadlock and command affected. Scope: global only
1205	More detailed information about the command being executed at the time of a deadlock. This trace flag was documented in SQL Server 7.0 Books Online, but was not documented in SQL Server 8.
1206	Used to complement flag 1204 by displaying other locks held by deadlock parties
1211	Disables lock escalation based on memory pressure, or based on number of locks. The SQL Server Database Engine will not escalate row or page locks to table locks. Using this trace flag can generate excessive numbers of locks. This can slow the performance of the Database Engine, or cause 1204 errors (unable to allocate lock resource) because of insufficient memory. For more information, see Lock Escalation (Database Engine) . If both trace flag 1211 and 1224 are set, 1211 takes precedence over 1224. However, because trace flag 1211 prevents escalation in every case, even under memory pressure, we recommend that you use 1224. This helps avoid "out-of-locks" errors when many locks are being used. Scope : global or session
1216	SQL 7 - Disables Health reporting. Lock monitor when detects a (worker thread) resource level blocking scenario. If a SPID that owns a lock is currently queued to the scheduler, because all the assigned worker threads have been created and all the assigned worker threads are in an un-resolvable wait state, the following error message is written to the SQL Server error log: Error 1223: Process ID %d:%d cannot acquire lock "%s" on resource %s because a potential deadlock exists on Scheduler %d for the resource. Process ID %d:% d holds a lock "%h" on this resource.
1222	Returns the resources and types of locks that are participating in a deadlock and also the current command affected, in an XML format that does not comply with any XSD schema. Scope : global only
1224	Disables lock escalation based on the number of locks. However, memory pressure can still activate lock escalation. The Database Engine escalates row or page locks to table (or partition) locks if the amount of memory used by lock objects exceeds one of the following conditions: · 40% of the memory that is used by Db Engine, exclusive of memory allocation using Address Windowing Extension (AWE). This is applicable when the locks parameter of sp_configure is set to 0. · Forty percent of the lock memory that is configured by using the locks parameter of sp_configure . If both trace flag 1211 and 1224 are set, 1211 takes precedence over 1224. However, because trace flag 1211 prevents escalation in every case, even under memory pressure, we recommend that you use 1224. This helps avoid "out-of-locks" errors when many locks are being used. Note: Lock escalation to the table- or HoBT-level granularity can also be controlled by using the LOCK_ESCALATION option of the ALTER TABLE statement. Scope: global or session
1261	SQL 8 - Disables Health reporting. Lock monitor when detects a (worker thread) resource level blocking scenario. If a SPID that owns a lock is currently queued to the scheduler, because all the assigned worker threads have been created and all the assigned worker threads are in an un-resolvable wait state, the following error message is written to the SQL Server error log: Error 1229: Process ID %d:%d owns resources that are blocking processes on scheduler %d.
1400	Enables the creation of the database mirroring endpoint, which is required for setting up and using database mirroring. This trace flag is allowed only when using the –T.
1462	Turns off log stream compression and effectively reverts the behavior back to ver 9.
1603	Use standard disk I/O (i.e. turn off asynchronous I/O).
1609	Turns on the unpacking and checking of remote procedure call (RPC) information in Open Data Services. Used only when applications depend on the old behavior.
1610	Boot the SQL dataserver with TCP_NODELAY enabled.
1611	If possible, pin shared memory -- check errorlog for success/failure.
1704	Prints information when a temporary table is created or dropped.
1717	Causes new objects being created to be system objects.
1806	Disables instant file initialization.
1807	Allows creating a database file on a mapped or UNC network location. unsupported under SQL Server 7 & 8.
2301	Enables advanced optimizations that are specific to decision support queries. This option applies to decision support processing of large data sets.
2330	Stops the collection of statistics for sys.db_index_usage_stats.
2382	Statistics collected for system tables.
2389	SQL 9 – Tracks the nature of columns by subsequent statistics updates. When SQL Server determines that the statistics increase three times, the column is branded ascending. The statistics will be updated automatically at query compile.
2390	Does the same like 2389 even if ascending nature of the column is not known and -- never enable without 2389.
2440	Parallel query execution strategy on partitioned tables. SQL 9 – uses a single thread per partition parallel query execution strategy. In ver. 10, multiple threads can be allocated to a single partition, thus improving the query’s response time.
2505	Prevents DBCC TRACEON 208, SPID 10 errors from appearing in the error log.
2508	Disables parallel non-clustered index checking for DBCC CHECKTABLE.
2509	Used with DBCC CHECKTABLE.html to see the total count of ghost records in a table
2520	Force DBCC HELP to return syntax of undocumented DBCC statements. If 2520 is not turned on, DBCC HELP will refuse to give you the syntax stating: "No help available for DBCC statement 'undocumented statement'".
2528	Disables parallel checking of objects by DBCC CHECKDB, CHECKFILEGROUP and CHECKTABLE. By default, the degree of parallelism is automatically determined by the query processor. The maximum degree of parallelism is configured just like that of parallel queries. For more information, see max degree of parallelism Option . Parallel DBCC should typically be left enabled. For DBCC CHECKDB, the query processor reevaluates and automatically adjusts parallelism with each table or batch of tables checked. Sometimes, checking may start when the server is almost idle. An administrator who knows that the load will increase before checking is complete may want to manually decrease or disable parallelism. Disabling parallel checking of DBCC can cause it to take much longer to complete and if DBCC is run with the TABLOCK feature enabled and parallelism set off, tables may be locked for longer periods of time. Scope : global or session
2537	SQL 9 & 10. Allows function ::fn_dblog to look inside all logs (not just the active log).
2542	SQL 8 – Used with Sqldumper.exe to get certain dumps. In range 254x – 255x.
2551	Adds additional information to the dump file.
2701	Sets the @@ERROR system function to 50000 for RAISERROR messages with severity levels of 10 or less. When disabled, sets the @@ERROR system function to 0 for RAISERROR messages with severity levels of 10 or less.
2861	Cache query plans for queries that have a cost of zero or near to zero.
3001	Stops sending backup entries into MSDB.
3004	Gives out more detailed information about restore & backup activities.
3031	SQL 9 - will turn the NO_LOG and TRUNCATE_ONLY options into checkpoints in all recovery modes.
3104	Causes SQL Server to bypass checking for free space.
3111	Cause LogMgr::ValidateBackedupBlock to be skipped during backup and restore operations.
3205	If a tape drive supports hardware compression, either the DUMP or BACKUP statement uses it. With this trace flag, you can disable hardware compression for tape drivers. This is useful when you want to exchange tapes with other sites or tape drives that do not support compression. Scope : global or session
3213	Trace SQL Server activity during backup process so that we will come to know which part of backup process is taking more time.
3222	Disables the read ahead that is used by the recovery operation during roll forward operations.
3226	With this trace flag, you can suppress BACKUP COMPLETED log entries going to WIN and SQL logs.
3231	SQL 8 & 9 - will turn the NO_LOG and TRUNCATE_ONLY options into no-ops in FULL/BULK_LOGGED recovery mode, and will clear the log in SIMPLE recovery mode.
3282	SQL 6.5 – Used after backup restoration fails refer to microsoft for article Q215458.
3422	Cause auditing of transaction log records as they're read (during transaction rollback or log recovery). This is useful because there is no equivalent to page checksums for transaction log records and so no way to detect whether log records are being corrupted e careful with these trace flags - I don't recommend using them unless you are experiencing corruptions that you can't diagnose. Turning them on will cause a big CPU hit because of the extra auditing that's happening.
3502	Tracks CHECKPOINT - Prints a message to the log at the start and end of each checkpoint.
3503	Indicates whether the checkpoint at the end of automatic recovery was skipped for a database (this applies only to read-only databases ).
3504	For internal testing. Will raise a bogus log-out-of-space condition from checkpoint()
3505	Disables automatic checkpoints. May increase recovery time and can prevent log space reuse until the next checkpoint is issued. Make sure to issue manual checkpoints on all read/write databases at appropriate time intervals. Note does not prevent the internal checkpoints that are issued by certain commands, such as BACKUP .
3601	Stack trace when error raised. Also see 3603
3602	Records all error and warning messages sent to the client.
3603	SQL Server fails to install on tricore, Bypass SMT check is enabled, flags are added via registry. Also see 3601.
3604	Sends trace output to the client. This trace flag is used only when setting trace flags with DBCC TRACEON and DBCC TRACEOFF.
3605	Sends trace output to the error log. (if SQL Server is started from CMD output also appears on the screen)
3607	Trace flag 3607 skips the recovery of databases on the startup of SQL Server and clears the TempDB. Setting this flag lets you get past certain crashes, but there is a chance that some data will be lost
3608	Prevents SQL Server from automatically starting and recovering any database except the master database. Databases will be started and recovered when accessed. Some features, such as snapshot isolation and read committed snapshot, might not work.
3609	Skips the creation of the tempdb database at startup. Use this trace flag if the device or devices on which tempdb resides are problematic or problems exist in the model database.
3610	SQL 9. Divide by zero to result in NULL instead of error.
3625	Limits the amount of information returned in error messages. For more information, see Metadata Visibility Configuration . Scope : global only
3626	Turns on tracking of the CPU data for the sysprocesses table.
3640	Eliminates the sending of DONE_IN_PROC messages to the client for each statement in a stored procedure. This is similar to the session setting of SET NOCOUNT ON, but when set as a trace flag, every client session is handled this way.
3689	Logs extended errors to errorlog when network disconnect occurs, turned off by default. Will dump out the socket error code this can sometimes give you a clue as to the root cause.
3913	SQL 7/8 – SQL Server does not update the rowcnt column of the sysindexes system table until the transaction is committed. When turned on the optimizer gets row count information from in-memory metadata that is saved to sysindexes system table when the transaction commits.
4013	This trace flag writes an entry to the SQL Server error log when a new connection is established. For each connection that occurs, the trace flag writes two entries that look like this: Login: sa saSQL Query Analyzer(local)ODBCmaster, server process ID (SPID): 57, kernel process ID (KPID): 57. Login: sa XANADUsaSQL Query Analyzer(local)ODBCmaster, server process ID (SPID): 57, kernel process ID (KPID): 57.
4022	If turns on, then automatically started procedures will be bypassed.
4029	Logs extended errors to errorlog when network disconnect occurs, turned off by default. Will dump out the socket error code this can sometimes give you a clue as to the root cause.
4030	Prints both a byte and ASCII representation of the receive buffer. Used when you want to see what queries a client is sending to SQL Server. You can use this trace flag if you experience a protection violation and want to determine which statement caused it. Typically, you can set this flag globally or use SQL Server Enterprise Manager. You can also use DBCC INPUTBUFFER.
4031	Prints both a byte and ASCII representation of the send buffers (what SQL Server sends back to the client). You can also use DBCC OUTPUTBUFFER.
4032	Traces the SQL commands coming in from the client. The output destination of the trace flag is controlled with the 3605/3604 trace flags.
4101	SQL 9 - Query that involves an outer join operation runs very slowly. However, if you use the FORCE ORDER query hint in the query, the query runs much faster. Additionally, the execution plan of the query contains the following text in theWarnings column: NO JOIN PREDICATE Turn these trace flags after HOTFIX is applied (SP2 CUP4)
4121
4606	Over comes SA password by startup. Refer to Ms article 936892.
4612	Disable the ring buffer logging - no new entries will be made into the ring buffer.
4613	Generate a minidump file whenever an entry is logged into the ring buffer.
4616	Makes server-level metadata visible to application roles. In SQL Server, an application role cannot access metadata outside its own database because application roles are not associated with a server-level principal. This is a change of behavior from earlier versions of SQL Server. Setting this global flag disables the new restrictions, and allows for application roles to access server-level metadata. Scope : global only
5302	Alters default behavior of select…INTO (and other processes) that lock system tables for the duration of the transaction. This trace flag disables such locking during an implicit transaction.
6527	Disables generation of a memory dump on the first occurrence of an out-of-memory exception in CLR integration. By default, SQL Server generates a small memory dump on the first occurrence of an out-of-memory exception in the CLR. The behavior of the trace flag is as follows: · If this is used as a startup trace flag, a memory dump is never generated. However, a memory dump may be generated if other trace flags are used. · If this trace flag is enabled on a running server, a memory dump will not be automatically generated from that point on. However, if a memory dump has already been generated due to an out-of-memory exception in the CLR, this trace flag will have no effect. Scope : global only
7103	Disable table lock promotion for text columns. Refer to Ms article - 230044
7300	Retrieves extended information about any error you encounter when you execute a distributed query.
7501	Dynamic cursors are used by default on forward-only cursors. Dynamic cursors are faster than in earlier versions and no longer require unique indexes. This flag disables the dynamic cursor enhancements and reverts to version 6.0 behavior.
7502	Disables the caching of cursor plans for extended stored procedures.
7505	Enables version 6.x handling of return codes when calling dbcursorfetchex and the resulting cursor position follows the end of the cursor result set.
7525	Reverts to the SQL Server 7 behavior of closing nonstatic cursors regardless of the SET CURSOR_CLOSE_ON_COMMIT state in SQL Server 8.
7601	Turns on full text indexing. Together these four gather more information about full text search (indexing process) to the error log.
7603
7604
7605
7646	SQL 10. Avoids blocking when using full text indexing. An issue we experienced that full text can be slow when there is a high number of updates to the index and is caused by blocking on the docidfilter internal table.
7806	Enables a dedicated administrator connection (DAC) on SQL Svr Express. By default, no DAC resources are reserved on SQL Server Express.
8004	SQL server to create a mini dump once you enable 2551 and a out of memory condition is hit.
8011	Disables the collection of additional diagnostic information for Resource Monitor. You can use the information in this ring buffer to diagnose out-of-memory conditions. Scope: GLOBAL.
8012	Records an event in the schedule ring buffer every time that one of the following events occurs: · A scheduler switches context to another worker. · A worker is suspended or resumed. · A worker enters the preemptive mode or the non-preemptive mode. You can use the diagnostic information in this ring buffer to analyze scheduling problems. For example, you can use the information in this ring buffer to troubleshoot problems when SQL Server stops responding. Trace flag 8012 disables recording of events for schedulers. You can turn on trace flag 8012 only at startup.
8018	Disables the creation of the ring buffer, and no exception information is recorded. The exception ring buffer records the last 256 exceptions that are raised on a node. Each record contains some information about the error and contains a stack trace. A record is added to the ring buffer when an exception is raised.
8019	Disables stack collection during the record creation, has no effect if trace flag 8018 is turned on. Disabling the exception ring buffer makes it more difficult to diagnose problems that are related to internal server errors. You can turn on trace flag 8018 and trace flag 8019 only at startup.
8020	SQL Server uses the size of the working set when SQL Server interprets the global memory state signals from the operating system. Trace flag 8020 removes the size of the working set from consideration when SQL Server interprets the global memory state signals. If you use this trace flag incorrectly, heavy paging occurs, and the performance is poor. Therefore, contact Microsoft Support before you use. You can turn on trace flag 8020 only at startup
8033	SQL 9 – disable the reporting of CPU Drift errors in the SQL Server errorlog like time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
8202	Used to replicate UPDATE as DELETE/INSERT pair at the publisher. i.e. UPDATE commands at the publisher can be run as an "on-page DELETE/INSERT" or a "full DELETE/INSERT". If the UPDATE command is run as an "on-page DELETE/INSERT," the Logreader send UDPATE command to the subscriber, If the UPDATE command is run as a "full DELETE/INSERT," the Logreader send UPDATE as DELETE/INSERT Pair. If you turn on trace flag 8202, then UPDATE commands at the publisher will be always send to the subscriber as DELETE/INSERT pair.
8206	Supports stored procedure execution with a user specified owner name for SQL Server subscribers or without owner qualification for heterogeneous subscribers in SQL Server 8.
8207	Enables singleton updates for Transactional Replication, released with SQL Server 8 SP 1.
8501	Writes detailed information about Ms-DTC context & state changes to the log.
8599	Allows you to use a savepoint within a distributed transaction.
8602	Ignore index hints that are specified in query/procedure.
8679	Prevents the SQL Server optimizer from using a Hash Match Team operator.
8687	Used to disable query parallelism.
8721	Dumps information into the error log when AutoStat has been run.
8722	Disable all other types of hints. This includes the OPTION clause.
8744	Disables pre-fetching for the Nested Loops operator. Incorrect use of this trace flag may cause additional physical reads when SQL Server executes plans that contain the Nested Loops operator. For more information about the Nested Loops operator, see the "Logical and physical operators reference" topic in SQL Server 9 BOL. You can turn on trace flag 8744 at startup or in a user session. When you turn on trace flag 8744 at startup, the trace flag has global scope. When you turn on trace flag 8744 in a user session, the trace flag has session scope.
8755	Disable any locking hints like READONLY. By setting this, you allow SQL Server to dynamically select the best locking hint for the query.
8783	Allows DELETE, INSERT, and UPDATE statements to honor the SET ROWCOUNT ON setting when enabled.
8816	Logs every two-digit year conversion to a four-digit year.
9134	SQL 8 – Does additional reads to test if the page is allocated & linked correctly this checks IAM & PFS. Fixes error 601 for queries under Isolation level read uncommitted.
9268	SQL 8 – When SQL Server runs a parameterized query that contains several IN clauses, each with a large number of values, SQL Server may return the following error message after a minute or more of high CPU utilization: Server: Msg 8623, Level 16, State 1 Internal Query Processor Error: The query processor could not produce a query plan. Contact your primary support provider for more information. http://support.microsoft.com/kb/325658 Enabling this trace flag activates the hotfix.

更多trace flag可以参考：http://www.cnblogs.com/Amaranthus/archive/2012/08/01/2619045.html

本文链接地址：https://www.dbainfo.net/sql-server-trace-flags.htm；

本文为dbainfo个人原创，请在尊重作者劳动成果的前提下进行转载；

转载务必注明原始出处 : Sybase数据库技术，数据库恢复专家；

对《SQL Server TRACE FLAGS》有何疑问或见解，请在本文下方发表；

对网站还有其他问题或建议，请提交在留言板，谢谢！

2009-11-18 -- 整理的Sybase Dbcc traceflags (0)

整理的Sybase Dbcc traceflags

dbainfo — Wed, 18 Nov 2009 13:55:13 +0000

从多个渠道收集来的sybase trace flag

With dbcc traceflags you can do many different things, like change the behaviour of the server, see why a certain query plan is choosen or fine-tune the optimizer.
This page shows you how to use them and provides a list of known traceflags.

You can set a traceflag in two ways
1.At boottime
Usually a server is booted through the runserver file. In this file (default location is $SYBASE/$SYBASE_ASE/install) you can add a traceflag by specifying a -T flag and one or more comma separated values.
2.At run time
When you are logged in to ASE you can set a traceflag with the dbcc traceon command. Example:
dbcc traceon(3604)

You can specify multiple values, comma separated.
To turn a traceflag off, use traceoff
dbcc traceoff(3604)

Which traceflags are active

To see which traceflags are active for your own session use the dbcc traceflags command
dbcc traceflags

To see the traceflags of other sessions as well
dbcc traceflags(2)

List of known traceflags

Below you will find a list of currently known traceflags. But beware of the following:
WARNING
? Most traceflags are undocumented and not supported by Sybase, use at your own risk. Certain traceflags can severely harm your databases.
? Some traceflags are obsolete and are replaced by configuration parameters.
? Certain traceflags should be used when you start the server, others are meant for a specific session, when known this is indicated in the list.
? Experiment first on a test server, use only on production systems when either the traceflag is documented by Sybase or when you have consulted Sybase Technical Support.

List of dbcc traceflags

-----------------------------------------------------------------------------------
100 Display a parse tree for each command
108 Allow dynamic and host variables in create view statements
116 Print the text of the abstract query plan. Supported by Sybase, see documentation
200 Display messages about the before image of the query-tree
201 Display messages about the after image of the query tree
208 Show types of locks taken
217 Display a warning message for using the T-SQL extension of queries with grouped aggregates and columns in the select list which are not in the GROUP BY clause.
241 Compress all query-trees when ASE is started
243 Do not expand select * to column names when creating a compiled object
244 When set, the maximum length of the returned value of str_replace() is 16384, otherwise it is 255
260 Reduce TDS (Tabular Data Stream) overhead in stored procedures. Turn off done-in-behaviour packets. See also Send doneinproc tokens.
291 Changes the hierarchy and casting of datatypes to pre-11.5.1 behaviour. There was an issue is some very rare cases where a wrong result could occur, but that's been cleared up in 11.9.2 and above.
292 Never send doneinproc tokens. See also Send doneinproc tokens.
298 Display an error message when a query uses a correlated variable as an inner or outer member of an outer join.
299 Do not recompile a stored procedure that inherits a temp table from a parent procedure.
302 Print trace information on index selection, supported by Sybase, see documentation
303 Display optimizer OR strategy
304 Revert special "or" optimizer strategy to the strategy used in pre-System 11 (this traceflag resolved several bug issues in System 11, most of these bugs are fixed in ASE 11.0.3.2)
310 Show the plan as choosen by the optimizer, as well as I/O costs. Supported by Sybase see documentation
311 Display optimizers expected I/O cost
317 Show all considered plans. Supported by Sybase, see documentation
319 Display optimizer reformatting strategy
320 Turn off join order heuristics
321 Display optimizers reformatting strategy briefly
324 Turn off the like optimization for ad-hoc queries using local variables
326 Instructs the server to use arithmetic averaging when calculating density instead of a geometric weighted average when updating statistics. Useful for building better stats when an index has skew on the leading column. Use only for updating the stats of a table/index with known skewed data.
329 Turns on a strategy for fast first row return for queries using cursors with an ORDERBY.
333 Disables min-max optimization
334 Enable merge joins
353 Turn off transitive closure
362 Will disable delta project
364 Use range density instead of total density
370 Use min-max index as an alternative to the table scan for single table queries. Does not perform aggregation optimization for joins.
384 Enable JTC
396 Use min-max optimization for single table queries.
450 Sort a group by operation in the order of the groups
516 Print mapping between xchg operators and worker processes when using parallel execution. Supported by Sybase, see documentation
526 Print semi-graphical execution operator tree when showplan is enabled. Supported by Sybase, see documentation
589 Close a cursor implicitly during a cursor fetch and after an error was hit.
602 Prints out diagnostic information for deadlock prevention.
603 Prints out diagnostic information when avoiding deadlock.
615 When a read of a page does not indicate it's right identity a second read is done. When the identity is now correct the related device is suspect and ASE turns on additional diagnostic checks. The check can be turned off with the traceflag.
646 Turn off the new space allocation method as introduced in 12.5.3 for partitioned DOL tables
693 Turn off some blocking optimizations in scans such as skipping uncommitted inserts and skipping or returning uncommitted updates based on info about what columns were updated.
695 Turn off update_mode optimization completely for multi-row updates (bugfix 97199)
699 Turn off transaction logging
712 Disable procedure cache optimisation
712 Turn off engine local memory optimization. Engine local cache enhancements were added to ASE, and disabling this should not make a noticeable impact on ASE servers running with less than 5 engines. (no benchmarks). (see case 11270180)
720 disable the warning msg "memory usage in procedure headers XXX does not match memory usage count in Pss (XXXX) for server process id XXXX." This error is reported when Adaptive Server cleans up after normal completion of a batch process and determines that the memory usage tracked by the procedure header does not match the usage total maintained in the PSS. No action is required, since this is an informational message and does not result in any incorrect behavior. Upon detecting the memory count mismatch, Adaptive Server corrects the appropriate counter, completes the cleanup tasks, and continues processing. (available since ASE 12.0.0.4 ESD#1)
722 ASE (debug version) will perform additional checks on the heap memory to detect possible memory corruption.
833 Do not report Msg 880 "Your query is blocked because it tried to write and database '' is in quiesce state. Your query will proceed after the DBA performs QUIESCE DATABASE RELEASE.".
990 Allow only access to the server with the "sa" account. Supported by Sybase, see documentation
1116 Suppress Msg 1131. (The OAM page does not belong to object with index.....)
1202 Also show the blocked lock requests in master..syslocks
1204 Print deadlock information into errorlog
1205 Prints deadlock information by printing stacktraces.
1206 Disable lock promotion.
1212 Shows info about locks granted and released
1213 Used with dbcc object_stats
1217 Show info about locks being acquired
1603 Turns off async i/o and forces standard unix io. Can be useful if symptoms include transient corruption errors that may be caused by bad drives or controllers.
1605 Start secondary engines by hand
1606 Create a debug engine start file. This allows you to start up a debug engine which can access the server's shared memory for running diagnostics.
1608 Instructs server engine 0 to not on-line any other dataserver engines
1610 Boot the server with TCP_NODELAY enabled.
1611 If possible, pin shared memory -- check errorlog for success/failure.
1613 Set affinity of the ASE engine's onto particular CPUs usually pins engine 0 to processor 0, engine 1 to processor 1, etc
1615 SGI only: turn on recoverability to filesystem devices.
1625 Linux only: Revert to using cached filesystem I/O. By default, ASE on Linux opens filesystem devices using O_SYNC, unlike other Unix based releases, which means it is safe to use filesystems devices for production systems.
1630 SuSE 32 bit Linux (SuSE 9 SP1 or later), ASE incorrectly identifies AIO to be KAIO while using Posix AIO. Can lead to ASE hang. Start with this trace flag.
1642 Reserve one third of the sockets for EJB.
1649 Allow the server to run Linux Kernel Async I/O. For Linux kernel 2.6 and above, to force low level kernel async I/O.
1650 Allow copying encrypted password strings between platforms (e.g. Solaris to Linux)
2205 Show HA debugging output, supported by Sybase see documentation
2209 Used when upgrading ASE configured with high availability
2512 Instructs dbcc checkalloc to skip the syslogs table during processing.
2513 Instructs dbcc checkalloc, tablealloc and indexalloc to check for whether foreign objects are stranded on a particular segment within a database. Supported by Sybase, see documentation
2703 When using update statistics with sampling and the index/column does not have existing statistics, set join density and total density to values from the sample rather then to defaults.
3100 Load a database even when the characterset or sort order of a dump file is incompatible with the server.
3199 When ONLINE DATABASE fails with Msg 2610 (Could not find leaf row in nonclustered index partition ...) after a cross-platform database load, set the traceflag on, reload the dump and online again.
3300 Display each log record that is being processed during recovery. You may wish to redirect stdout because it can be a lot of information.
3453 During the redo pass, allow the page timestamp to fall between the log old timestamp and the log new timestamp and also for the page timestamp to be behind the log old timestamp. In such cases, fix up the page timestamp to be the log old timestamp so that the current log record will be redone. Used to compensate for bugs in the recovery of sort. This trace flag MUST only be used in exceptional cases, and only where it is known that modifying the page timestamp is the correct thing to do. If not used wisely, data corruptions can occur. (see case 11159541)
3474 Disable tuning of buffer pools on recovery
3500 Disable checkpointing.
3502 Write an entry in the errorlog when a databases is checkpointed
3504 For internal testing. Will raise a bogus log-out-of-space condition from checkpoint()
3601 Write a stacktrace to the errorlog every time an error is raised.
3604 Send trace output to the session of the client. Supported by Sybase see documentation
3605 Send trace output to the errorlog of the server. Supported by Sybase see documentation
3607 Do not start recovery when booting ASE.
3608 Recover only the master database. Do not clear tempdb or start up checkpoint process.
3609 Recover all databases. Do not clear tempdb or start up checkpoint process.
3610 Pre-System 10 behaviour: divide by zero to result in NULL instead of error
3620 Do not kill infected processes.
3635 Print diagnostic information (see case 11257124, to get info for LDAP login problem). Trace Flag 3635 Diagnostics are written to the console that started ASE. There are not written to the errorlog, even if 3605 is turned on.
3706 Performance improvement of drop table in tempdb.
3708 By default ASE (12.5.3 onwards) will release the system catalog locks during the drop of user tables in tempdb when not in DDL-IN-TRAN mode after the commit of the transaction but before post commit work started. Turns off the default behaviour
3710 Improve the performance of DROP INDEX and CREATE INDEX by releasing the system catalog locks when not in DDL-IN-TRAN mode after the commit of the transaction but before post commit work started.
4001 Display a message in the errorlog when a loginrecord is recieved
4012 Don't spawn chkptproc.
4013 Write a message to the errorlog when a login takes place.
4020 Boot without recover.
4044 Allows to log into ASE when the "sa" login is locked
4063 used by 12.0 server to turn on sqldbgr RPCs
4066 Turn off the check for invalid data being sent from a connecting client. (see case 11239779: After ugraded to ASE 1253 to 1251, getting errors when logging into application: The packet size (0) specified at login time is illegal. Legal values are between 512 and 512.)
4072 Disable the global login trigger
4073 Export the result of certain "set" command within a login trigger to the session.
4080 When an UPDATE using tsequal() is done within a stored procedure, tsequal() no longer returns a timestamp value unless the trace flag is set.
4404 to disable pushdown of Union views. Change the order of the union view and the other view in the from clause, so that the union view is the last entry in the from clause
4413 Trace queries in a 12.5 server that are join-order dependent.
4419 In some cases, outer join on view or derived table with CASE expression may perform slower due to view materialization.The workaround is to use traceflag 4419.
5303 Select into a temporary table will be executed without the table being sliced
5304 Disable the large I/O and large allocation changes done under 279883-1.
5101 Forces all I/O requests to go through engine 0. This removes the contention between processors but could create a bottleneck if engine 0 becomes busy with non-I/O tasks.
5102 Prevents engine 0 from running any non-affinitied tasks.
7103 Disable table lock promotion for text columns.
7408 Force the server to scan *log segment* allocation pages; to recalculate free log space rather than use saved counts at boot time. (see case 11195087)
7409 Force the server to scan *data* segment allocation pages; to recalculate free data page space rather than use saved counts at boot time. (see case 11195087)
7703 When assinging a value from a table into a local variable, go through the whole resultset rather than jump to last row and assing the value once.
7709 In 12.5.2, an insert inside a stored proc writes trailing white space when selecting from a char not null field. This can lead to strange results when when selecting data. The traceflag disables this padding.
7717 Disable check of client compatibility in ASE 15. See Version 15 client compatibility
7738 Support plan sharing of cached statements across different users.
7815 logs address connection requests and host / name lookups.
7824 Disable the master/query syntax in the interfaces file
7841 Make ASE IPv6 aware
7844 Enable/disable concurrent Kerberos authentication
8003 prints info on RPC calls
8203 Display statement and transaction locks on a deadlock error.
8399 Instructs the dbcc monitor command to insert a valid description into the field_name column in the sysmonitors table. Not intended for use by users. Appears in the errorlog when sp_sysmon is used.
9217 When set, RepAgent will not stop after reporting error 9289 due to an inconsistent log record found. Instead it will attempt to continue after reporting error 9290 in the error log. Supported by Sybase, see documentation
9531 Dump expensive buffer allocation analysis
10303 Invoke set completion of object ownership methodology and object resolution from old procedural ownership
11201 Logs client connect events, disconnect events, and attention events. Supported by Sybase, see documentation
11202 Logs client language, cursor declare, dynamic prepare, and dynamic execute-immediate text. Supported by Sybase, see documentation
11203 Logs client rpc events. Supported by Sybase, see documentation
11204 Logs all messages routed to client. Supported by Sybase, see documentation
11205 Logs all interaction with remote server. Supported by Sybase, see documentation
11206 Show messages about query processing for file access. Supported by Sybase, see documentation
11207 Log the processing of text and image datatypes from remote servers. Supported by Sybase, see documentation
11208 Prevents the create index and drop table statements from being transmitted to a remote server. sysindexes is updated anyway. Supported by Sybase, see documentation
11209 When running "update statistics" on remote tables update only the rowcount. Supported by Sybase, see documentation
11210 Disables Component Integration Services enhanced remote query optimization.
11211 Prevents the drop table syntax from being forwarded to remote servers if the table was created using the create table at location syntax. Supported by Sybase, see documentation
11212 Prevents escape on underscores in table names. Supported by Sybase, see documentation
11213 Prevents generation of column and table constraints. Supported by Sybase, see documentation
11214 Disables Component Integration Services recovery at start-up. Supported by Sybase, see documentation
11215 Sets enhanced remote optimization for servers of class db2.
11216 For the session, disables enhanced remote optimization. Supported by Sybase, see documentation
11217 For the server, disables enhanced remote optimization. Supported by Sybase, see documentation
11218 Any query that is part of a declare cursor command, and that references proxy tables, is read only by default. Supported by Sybase, see documentation
11220 Disables constraint checking of remote tables on the local server. This avoids duplicate checking. Setting this trace flag on ensures that queries are not rejected by the quickpass mode because of constraints. (spid) Supported by Sybase, see documentation
11221 Disables alter table commands to the remote server when ON. This allows users to modify type, length, and nullability of columns in a local table without changing columns in the remote table. Use trace flag 11221 with caution. It may lead to tables that are “out of sync.” (spid). Supported by Sybase, see documentation
11223 Disables proxy table index creation during create existing table or create proxy_table command execution. If this flag is set on, no index metadata is imported from the remote site referenced by the proxy table, and no indexes for the proxy table are created. This trace flag should be used with care and turned off when no longer necessary. (global) Supported by Sybase, see documentation
11228 A 2762 error, "CREATE TABLE command is not allowed within multiple statement transaction" may be reported when executing a SQL INSERT..SELECT from proxy table mapped to a RPC. This traceflag has to be turned on to allow CREATE TABLE command in the remote procedure (for the session)
11229 Use pre-12.5.3 behaviour to import statistics for proxy tables. Supported by Sybase, see documentation
11231 CIS: Connections to remote servers are not disconnected and remain engine affinitied until the client session terminates. The connections can now be dropped and detached from an engine after executing a statement to the remote server by enabling this flag. Exceptions are when the statement is participating in cursor, transaction or stored procedure operations; or when ASE is in either HA failover or failback states.
11232 A 2762 error, "CREATE TABLE command is not allowed within multiple statement transaction" may be reported when executing a SQL INSERT..SELECT from proxy table mapped to a RPC. This traceflag has to be turned on to allow CREATE TABLE command in the remote procedure (serverwide)
11299 Allows connection information to be logged when a connection to a remote server fails. Supported by Sybase, see documentation
11906 Informational messages from REORG will no longer be printed to the errorlog.
12628 Data insertion into DOL tables having nonclustered index will be done with the index prepend mode splits disabled, in order to improve disk space utilization.
15302 When a subquery appears in the ON clause of an outer join query, the performance may not be efficient. ASE will do optimization for subquery attachment to achieve more favorable performance when turned on.
15303 Possible performance improvement on a SELECT statement when a BIT column is involved in the WHERE clause.
15304 CR 422003: A SELECT statement using a LIKE clause with NULL variables returns Msg 712. Workaround for 'unable to allocate 0 bytes to heap' bug fixed in 12.5.3 ESD7.
15381 When set, the warning message 307, "Index specified as optimizer hint in the FROM clause of table does not exist. Optimizer will choose another index instead." is disabled.
15382 Disable "special OR strategy" (see release notes for the fine details)
15556 Allow dump and load in ASE cluster edition with multiple instances active
-----------------------------------------------------------------------------------
————————————————————————————————
—- 本文为andkylee个人原创，请在尊重作者劳动成果的前提下进行转载；
—- 转载务必注明原始出处 : http://www.dbainfo.net
—- 关键字： sybase trace flag 调试参数
————————————————————————————————

本文链接地址：https://www.dbainfo.net/sybase-dbcc-traceflags.htm；