5. Trace flag 3608 (undocumented)
This trace flag skips automatic recovery (at startup) for all databases except the master database. Trace flag 3608 was documented in the SQL Server 6.5 Books Online, but was not documented in SQL Server 7.0.
6. Trace flag 3222 (undocumented)
If you drop, create, or rebuild indexes at the time of a database or transaction log backup, then subsequent attempts to load the backup may fail. This is because the recovery process can read ahead to increase the speed of recovery while rolling forward index maintenance activities. Trace flag 3222 disables the read ahead that is used by the recovery operation during roll forward operations.
For more information: http://support.microsoft.com/support/kb/articles/Q268/0/81.ASP
7. Trace flag 8202 (undocumented)
This trace flag is used to replicate UPDATE as a DELETE/INSERT pair during replication. 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 Log Reader Agent sends the UPDATE command to the subscriber. If the UPDATE command is run as a “full DELETE/INSERT,” the Log Reader Agent sends the UPDATE as a DELETE/INSERT pair. If you turn on trace flag 8202, then UPDATE commands at the publisher will be always sent to the subscriber as a DELETE/INSERT pair.
8. Trace flag 8816 (undocumented)
SQL Server can convert a two-digit year to a four-digit year, but Microsoft recommends using the the full four-digit year for all date operations. This trace flag logs every two-digit year conversion to a four-digit year. It can be useful to find year 2000 bugs in older programs.
Reprinted with the express written permission of the author. Copyright 2002.
]]>