I was monitoring a slowness issue into the database server with regarding sequential Store proc calls delay,
There is an application that call a database stored proc into a loop just one call after the other and stops at call No. 10, when I monitor those calls from the database server side using the profiler, the endtime of call No1 is basically the same of start time for call No.2 ... with 0 mille secs delay between one call and the other (this is when database is not showing slowness issues); but sometimes in peak time the database start facing slowness and the same profiler start showing delays from 100 millisecs to 250 millisecs between one call to another. the interest part is the actual execution time of the SP is behaving almost the same (from 2-5 millisecs more from the previous profiler)
There is already in place monitor from the source server to the database server Including NetworkTraffict and driver statistics trace.
But I was wondering if there is any way I can check something like port saturation for the SQL server port or any wait stats or perfmon counter or profiler who can show the calls that are arriving to SQL server and not getting executed right away?
Any suggestions I will really appreciate it.