Getting Top 10 expensive SQL Queries with fetching time included

Hi Zuher,

What do you mean by "fetching time", is it the time spent on fetch the database connection from the connection pool?

Wei

Hi Wei,

if you are executing a query inside MS ADO.NET  , ADO will start streaming you the first bits of the result .

we have seen that the sql statement execution time taking very small amount of time, but we still see that ADO.NET API is taking most of the transaction time due to the fact it add up the time till the last bit of the records streamed back to the application (fetching time of the result).

please look at this post to get the idea.

Database Time contribution tier

thanks

Hi 

any one has any news regarding this request???

Hi

Sorry for the late reply. In the moment we dont include the fetch or cursor time in SQL Executions. There are plans for this in future releases but right now we do not capture this as part of the ADO.NET Calls which show up in the Database Dashlet. We will capture some of this time through our Auto Sensors in case fetching is a performance problem.

One option you have is to place your own custom sensors on these fetch methods. This will show the time spent in these methods -> so - you will see it in the PurePath and also the Methods Dashlet -> not in the DB Dashlet though. But one thing to remember: if you have a lot of fetch calls then your PurePaths may grow significantly in size

Andi

Thanks Andi for the reply.

as you mentioned , it is not practical to do this as more than 70% of the calls to DB is having this fetching time and it is not possible to do it for all of them using custom censor unless of course we are lucky and the customer uses standard library for db access.

we already asked for any specific time or plan that include specific time when we will see this feature in Dynatrace,can you please check and give us some hunch about it .

one more thing , is this feature considered  RFE or you think it is a must in the product ??

thanks.