9 major steps to solve SQL Server faults

Translated from:

 

Http://www.databasejournal.com/features/mssql/article.php/3899851/article.htm

 

 

Step 1: gathering the facts collect fault information Step 2: Test in different environments and machines perform retest on different environments and machines Step 3: review the SQL Server Error Log to view the SQL Server Error Log Step 4: Review the event log to view the Operating System Log Step 5: Review the default trace to view the default SQL Server trace information

If the default tracing information is enabled, it automatically records the SQL server startup information when SQL server starts. This function is like a black box of an airplane. It records all changes to the configuration information of an SQL server instance. Check this information to see what changes have been made to the database during the fault. The default trace information and errorlog are stored in the same log folder, and the name is "log_xxx.trc". xxx here is a set of serial numbers. You can use profiler to open these files to view event records, or use the function "fn_trace_gettable" to process these files. You can use the following T-SQL:

Select * From fn_trace_gettable ('C: Program filesmicrosoft SQL servermssql.1mssqlloglog _ 155. trc', default );

Step 6: Review the change log to view the change log (for example Source codeLogs in management) Step 7: Develop a testing plan write test plan Step 8: backup database Step 9: perform additional tests and logging (Additional ??) Test and record change information