Another thread about SQL Server Profiler:
Identify SQL Server Performance Problems
I understand what you are talking about, but, as a rule, database optimization takes place at a more subtle level. If the database activity is initiated by the client, you should be able to use the existing client profiler to get the total time at each step, and then turn to low-hanging fruits (whether it is in the database or not).
When you need to profile a specific database step in detail, you can use profiler and tracing.
As a rule, access to the database has a certain level of detail, which is addressed on an individual basis, and the activity of the database is not linear, while all types of user access continue, while the profiler usually profiles the linear path of the code.
source share