From the big aspect, the bug is nothing more than: database bug; program bug.
SQL capture is useful in practical applications. For those unknown bugs, when you don't know where to go, capture SQL directly and execute SQL.
Application Details 1
The company does web-side projects and mobile-phone projects to integrate data. Project Manager to deploy the program, the database, IP, port configuration. Then go on-line test, the results found no data on the phone. The project manager then deploys the database to a new IP, port, mobile phone or no data. Then just wait for the product manager to return to the business after the solution. The Product Manager opens the SQL Server Profiler directly and then opens the phone side. SQL Server Profiler then captures the phone-side call. Then copy the SQL to the database for execution, and an error message appears. Solve this SQL error and the problem will be solved.
Application Details 2
I want to refactor the previous module, I also have the background of the previous code, but I do not understand what the previous background of SQL is what. "" Not a single comment, a full page of SQL, and a lot of if else for loops. These logic codes are written in SQL "". So I opened the SQL Server Profiler, opened the previous system, opened a page, and then captured a call to this page. Then copy this SQL into the database, change it, and implement the new function. Finally in the original module corresponding to each other, modify the SQL, complete the new function, complete the task.
Tips for use
There are many tricks on the web, some very low-level, such as what CPU, and performance; some are superficial, such as filtering other hosts, as long as the native calls the SQL.
I usually set a property, TextData.
What is 1.TextData?
TextData is the text of the SQL that you invoke. For example, you invoke SQL "" SELECT * from AAA "", then the database captures the TextData attribute that you call this behavior is "" SELECT * from AAA ".
2.TextData How to use
The above operation means capturing all SQL with "SELECT *" in the behavior.
Of course, the more specific you know about SQL, the more accurate the SQL you capture.
This is more accurate than the one above.
By using SQL Server Profiler, I can solve more difficult problems. Those who do not know what to do, have never heard of, can find ideas.
Quickly get started with SQL Server Profiler