Troubleshooting Methodology and Practices - SQL Server 2012 Internals and Troubleshooting - page 257

Implementing Resolution
The i nal step is to implement the resolution in production. Ensure that the change is documented
and any impact (such as service restarts) communicated. Note the behavior of the database or appli-
cation before and after the change, as well as exactly what change was made. Ensure that the success
criteria are met once the resolution is implemented, and share your results with the stakeholders.
Once the resolution is implemented and the solution is stabilized, carry out post-mortem analysis
and ensure that the root causes are communicated to relevant parties. Identify any other vulnerable
systems within the organization and communicate any lessons learned that may help you avoid a
recurrence of similar problems in the future.
SUMMARY
Coni dence and control are critical to successful troubleshooting. Developing a methodology
that can be consistently applied and rei ned is a valuable skill that enhances your value to an
organization.
Your attitude, knowledge of when and whom to ask for help, and ability to communicate with man-
agement and stakeholders are essential skills. In many job roles these skills are as important as tech-
nical skills to a successful career.
It doesn't matter if you are investigating a performance problem, resolving a security issue, or i xing
a connectivity problem. Use each scenario as an opportunity to implement and rei ne your trouble-
shooting approach.
Dei ne the problem, understand the exact circumstances under which the problem manifests itself,
and identify the problem's potential impact on the organization. Consider the end-to-end applica-
tion, hardware, and software scenario. Use the divide-and-conquer technique to isolate the problem,
eliminating or incriminating each component of the problem until you i nd the root cause. After
the cause is understood, develop a i x to resolve the issue, and then test it to validate that it doesn't
cause any undesirable consequences before implementing it in production.