Performance issues with your database are things that you might experience. To be able to troubleshoot and solve them, there are a few things that you should do. In this article, we will advise you on some SQL troubleshooting tips.
A SQl troubleshooting server database administrator can face a situation where he or she needs to solve a problem in the production environment. One of the most challenging task the administrator may encounter is solving an issue with an online service with high concurrent usage. Let’s say for example you are an administrator for Alibaba and the website goes unresponsive and it is showing the error message “Database Timeout”, what will you do? Remember that the way you handle the situation will either increase your value to the company or get you fired.
Now this is how you solve such an issue:
1st Step: Pull Yourself Together
You are the one tasked with solving the problem. This means that you have to be calm and thinking straight however stressful the environment is. You won’t be able to solve the problem even if you are the best IT technician in the firm.
2nd Step: Check the Application’s Database
After pulling yourself together, now you are to check the status of the system’s database. Below are so,e questions that you should ask yourself in order to solve the issue with the application.
Is there SQL Server locking and blocking?
Applications become unresponsive because of a number of reasons. One of the reasons being the app’s request to the DB being queued because a resource is blocked by a session. In this case, take a look at what code the session is executing and also its origin before killing it. It wouldn’t be efficient to just kill the session because another session might run the same code and the same issue will pop up. But if the blocking session is due to someone leaving a transaction open, then you can kill it. Run the following query to get more information on blocking:
CROSS APPLY sys.dm_exec_sql_text(sql_handle)
Are other applications running on the same server having issues?
Do not ignore this item. This is because if the server is the one with the problem, then you can easily tell that all other applications running on it will have problems. If you diagnose the server and you find that it has no issue, then we move to the next probing question which is did the app have any recent updates? If it did, then the issue could be with the update.