Shulou(Shulou.com)05/31 Report--

This article will explain in detail how to conduct a technical summary of database performance events. The content of the article is of high quality, so the editor will share it with you for reference. I hope you will have some understanding of the relevant knowledge after reading this article.

1. Use select * from sys.sysprocesses where spid > 50 and kpid 0 to see how many connections are currently in progress for the corresponding thread. In SQL Server, connections with SPID greater than 50 represent user connections, while kpid represents the corresponding thread ID. When the corresponding connection needs an operation to run, SQL Server allocates a thread to it for CPU scheduling. It is found that there are few connections with assigned threads in the system, indicating that the current system is relatively idle.

two。 Use select sum (open_tran) from sys.sysprocesses where spid > 50 to view the current

How many active transactions are there in the system. The number of active transactions in the current system is only about 50, which is not as high as SQC reported.

3. Use select * from sys.sysprocesses where spid > 50 and blocked 0 to see if there are any blockages in the current system. In SQL Server, if the system blocks, the blocked column is populated with SPID that blocks other connections. No blocking was found in the current environment.

4. There is no blocking in the collected PSSDIAG and there are no performance-related bottlenecks in the system as a whole.

5. In the information provided by PSSDIAG, we do not find that SQL Server has any blocking that affects our application

(BLOCK), and according to statistics in PSSDIAG, the UPDATE statement we followed (ranked second) was executed 133565 times in 10 minutes to grab information, with an average time of 0.000807S per item. The SELECT statement we looked at (ranked fourth) was executed 133592 times, with an average execution time of 0.000193s each. Another INSERT statement failed to rank in the top ten.

6. Overall, there are no significant performance bottlenecks in SQL Server. All related statements are executed at a high speed

Hurry up. If a problem is occurring while fetching PSSDIAG, the performance problem from PSSDIAG should not be on the SQL Server side.

This is the end of the technical summary on how to conduct database performance events. I hope the above content can be helpful to you and learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.