Microsoft KB Archive/277272

{|
 * width="100%"|

BUG: Trace Flags 3607, 3608, 3609 Omitted from Documentation in SQL Server 7.0 and 2000

 * }

Q277272

-

The information in this article applies to:


 * Microsoft SQL Server version 7.0
 * Microsoft SQL Server 2000 (all editions)

-

BUG #: 58540 (SQLBUG_70)

BUG #: 236759 (SHILOH_BUGS)

SYMPTOMS
Trace flags 3607, 3608, 3609 are quite useful in some troubleshooting situations when SQL Server does not start or when a database is affected. These trace flags were omitted from the SQL Server Books Online documentation, so this article documents those trace flags.

STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0 documentation.

Microsoft has confirmed this to be a problem in SQL Server 2000 documentation.

MORE INFORMATION
Trace flags 3607, 3608, 3609 provide you flexibility in troubleshooting or isolating a problem with starting SQL Server or for troubleshooting a problematic database.

This section documents the functionality of the trace flags and also provides examples of how you can use the trace flags.

Trace Flag Examples
The examples are provided for the purpose of illustrating the use the trace flags. They are not be applied in each and every situation that is similar in nature to the examples that follow. Each specific situation, problem or cause of a problem may require a different approach and therefore these trace flags must be applied with caution and proper understanding.

-T3607 Usage Example
Situation: Need to restore a backup of the master database after a problem with the master database that prevents you from starting SQL Server.


 * 1) Start SQL Server from a command prompt by using the following syntax:
 * 2) Open SQL Server Query Analyzer and restore a backup of the master database by using:
 * 3) Restart SQL Server because it was shut down automatically after the restore of the master database.

NOTE: For additional information about -c, -m, and -T4022, refer to SQL Server Books Online.

-T3608 Usage Example
Situation: A user database is affected, say by a disk failure, and SQL Server may not start as a result. You need to restore the user database from backup after all hardware issues are resolved.


 * 1) Start SQL Server by recovering the master database only by using the following syntax:
 * 2) Restore a backup of the affected user database by using the following command:
 * 3) Stop the server from the command prompt by pressing CTRL+C.
 * 4) Restart SQL Server from the Service Control Manager.

-T3609 Usage Example
Situation: The model database is marked suspect because its transaction log has filled up due to a lack of disk space. As a result, the tempdb database cannot be created and SQL Server does not start.


 * 1) Start SQL Server and bypass the creation of the tempdb database. To bypass the creation of the tempdb database, use the following:
 * 2) Use the SQL Server Query Analyzer to issue the following statement to truncate the log in the model database:
 * 3) Stop SQL Server from the command prompt by using CTRL+C.
 * 4) Restart SQL Server from the Service Control Manager.

If you are using SQL Server 2000 Named Instances, look up the syntax for starting a named instance from a command prompt. Refer to the How to start a named instance of SQL Server (Command Prompt) topic in SQL Server 2000 Books Online.

Additional query words: 3607 3608 3609 trace flags

Keywords : kbdocerr kbSQLServ700bug kbDSupport kbCodeSnippet kbSQLServ2000bug

Issue type : kbbug

Technology : kbSQLServSearch kbAudDeveloper kbSQLServ700 kbSQLServ2000Search kbSQLServ2000