This collection of topics provides background information about troubleshooting and resolving the most common errors that you may encounter when using Microsoft® SQL Server™. If you encounter a problem while running SQL Server, check the SQL Server error log for entries that might help identify the cause. In addition, if you encounter a problem during your compatibility testing of SQL Server version 7.0, see SQL Server Backward Compatibility Details. This list of changed features provides detailed information about each change, as well as recommendations on how to correct the problem. If you encounter a problem during regular use of SQL Server, use this series of topics to resolve the problem.
How you start SQL Server determines where SQL Server events are logged:
The SQL Server error log contains only SQL Server messages; the Windows NT application log contains messages for all applications and Microsoft BackOffice® services on the computer. Both logs include informational messages (such as startup data), and both record the date and time of all events automatically.
The default is to use both the Windows NT application log and the SQL Server error log.
Note References to the term “error log” later in this documentation refer to the specific error log that you are using. References to the term “server” later in this documentation refer to the specific computer running SQL Server.
By creating and testing a plan for disaster recovery, you minimize the amount of time needed on future troubleshooting and minimize down time. Disaster recovery assessment provides verification of the plan. It is achieved by getting sufficient hardware, providing the documented disaster recovery guidelines, and having a backup system administrator or database administrator (someone who is not involved with plan development) recover the system on this computer. Perform periodic disaster recovery assessments to verify the vitality of the current disaster recovery plan.
The importance of disaster recovery assessment cannot be overstated. What is the business risk if you cannot get your data back? What is the cost for each hour's delay in getting your system back up and running? Do not assume that your data is quickly recoverable. Understand the steps thoroughly ahead of time, and you will minimize the stress and uncertainty imposed by the circumstances of a future disaster.
As a starting point to troubleshooting a problem, review the latest SQL Server error log and the Windows NT application log. For more information about viewing both of these log files, see Monitoring the Error Logs.
Additional information about troubleshooting SQL Server can be found at http://www.microsoft.com.
Important This URL will work only if your computer has Internet browser software installed. Contact your support provider if you do not have Internet browser software.
As an additional troubleshooting resource, you might also consider subscriptions to Microsoft TechNet or the Microsoft Developer Network (MSDN™). These subscriptions include the Microsoft KnowledgeBase as well as other current information. For more information about subscribing to Microsoft TechNet, see http://www.microsoft.com/technet/. For more information about subscribing to MSDN, see http://www.microsoft.com/msdn/.
To minimize the effects of a server failure or other troubleshooting situation:
| SQL Server Backward Compatibility Details | Managing Permissions |
| Choosing a Backup and Restore Strategy | Planning to Back Up and Restore Databases |
| Database Maintenance Plan Wizard |