You might find only one environment is affected, a set of environments orĪll environments. Of times seasoned staff do not think about performing tests in separate This is aįact gathering exercise, but I spelled it out as a separate step because lots It is worth testing in different environments, if you have them. Armed with someįacts about the problem you can start to look for clues that might help You need to determine if any new system or applicationĬhanges were introduced that might have caused the problem. In addition to this, you need to know the last time the system was The timeframe around when the problem occurred, and whether or not it is stillĪ problem. You need to determine if it is system wide, or is it more localized toĪ particular application, or component of an application. Interview the customer, or programmer to understand how and when the problem Need to know what kind of problem is happening. The first step in any problem solving exercise is to gather the facts. Information gathering phase of your forensic analysis. Below are a set of steps you should consider when going through the System error messages and log records exist that might help you to diagnose the You also need to review log files to determine what kind of In order to diagnose a problem you first need to gather some informationĪbout the problem. Why your SQL Server instance is not behaving as it should, provided there areĮvent records associated with the problem you are trying to solve. Events in the event log may provide a quick answer to You can browse through the events one at a time Sometime when your system is having problems, event records will be written Notepad allows you to do string searches within large logįiles to quickly locate information. Notepad does not seem like much of a tool however, it can be used to openĭifferent log files. To create your own traces while troubleshooting a problem. It is amazing what you can find byĮxploring the default trace information. Profiler can be used to review the informationĬaptured from the default trace event. When SQL Server starts up, it starts a default trace event, provided theĭefault trace is enabled. Here is a list of those commonly used tools: In most cases, you should beĪble to find enough information using these tools to provide you with enoughĬlues to determine the cause of a particular problem. Troubleshooting, therefore I will cover the most common tools that areĪvailable within SQL Server and the Windows OS. IĬannot cover, nor do I know of all the tools you could possibly use for There are a number of different tools you can use for troubleshooting. Might go through to help troubleshoot a problem. I will cover some of the tools you can use to look for clues, and the steps you Some forensic analysis to determine the cause of the problem. Regardless of the problem, you will need to do However, sometimes we do unplug the network cable to prevent the machine fromīeing further contaminated, in rare cases. No, we do not put yellowĬaution tape around our servers, our network cables, and our desktop machines. (CSI) to uncover the root cause of the problem. In these situations, you need to act like a Crime Scene Investigator Through some problem solving steps to identify why the problem occurred, or is We all have problems that occur from time to time, where we need to work This article covers some of the tools you can use to look for clues, and the steps you might go through to help troubleshoot a SQL Server problem. DBAs often have a need to identify why a problem has occurred, or is occurring in their SQL Server database.
0 Comments
Leave a Reply. |