Databases Reference
In-Depth Information
This chapter focuses on a data-driven methodology for troubleshooting SQL Server problems, con-
sisting of the following three steps (the data collection and analysis may require multiple iterations
until the problem's cause is identii ed):
1.
Dei ne the problem.
2.
Iterate through:
➤
Data collection
➤
Data analysis
3.
Validate and implement resolution.
Investing time and effort to develop and rei ne a troubleshooting methodology helps improve the
efi ciency and speed with which you troubleshoot problems. Much like planning a trip, the route
and endpoint may vary, but identifying the destination and developing an approach to planning an
efi cient route is a distinct and different skill from driving itself. As you plan subsequent journeys,
you can rei ne your approach, becoming more adept at determining the quickest route and better at
estimating the length of time it takes between breaks and optimal departure time.
Troubleshooting SQL Server problems is similar to planning a long car trip. Whereas the rest of
this topic focuses on how the engine works and the troubleshooting skills themselves, this chapter
will help you develop a methodology for troubleshooting, which is as important as the tangible
troubleshooting skills themselves.
The topic provides one approach for troubleshooting, which you can use to develop or rei ne your
own approach. As you do so, consider roles and responsibilities, communication, reporting, and
seeking external help. Reaching a successful resolution can often be achieved by more than one
route. Identifying the path of least resistance while achieving the goal is the hallmark of a database
professional experienced in troubleshooting complex issues.
APPROACHING PROBLEMS
Developing a professional methodology to managing problems will lead to a less stressful time at
work, help make work more rewarding, and differentiate you from others. Although SQL Server is
a discrete technology, it is often the case that when problems occur, uncertainty arises regarding the
root cause, and problem scope is rarely well-dei ned. As such, issues can be passed around support
teams with little progress or ownership.
This section of the chapter describes a set of ten principles you can use in order to clearly and efi ciently
identify and resolve problems with SQL Server. Although many of the details here are not specii c to
SQL Server problems, they are good practices for troubleshooting many types of complex IT issues.
Ten Steps to Successful Troubleshooting
The following steps provide a detailed methodology for successful and efi cient incident resolution.
They intentionally separate identii cation of the root cause and issue resolution. These are differ-
ent tasks, and many situations require equal (or greater) effort to identify the root cause of an issue
Search WWH ::
Custom Search