Database Queries Not Segregated (DB Tuning)

Question

Hi all,
I was going through database dashboard of a mobile application.
Following are the snapshots:

You can see too many similar queries are being executed but DT is showing them as distinct rather than segregating them as one.
I would like to why is this happening? Is there something going wrong (with DB)? Please suggest.

[Also, here is an APM blog about DB tuning:

http://apmblog.dynatrace.com/2011/07/05/beyond-persistence-how-to-exploit-your-database-for-better-performance/

I hope this is not n+1 query problem though.]

Thanks in advance.

R.S.

Answer 1

Answer by Wolfgang G. · Feb 17, 2015 at 07:33 PM

Hi Rajesh,

I guess this is because those are in fact distinct queries as the LIKE clause is different. You can see in the executions column that some are executed multiple times and then the count is increased. I would suggest to rewrite the query to use a parameter also for LIKE

Hope that helps,

Wolfgang

0 · Share

Answer 2

Answer by Rajesh S. · Feb 17, 2015 at 08:53 PM

Thanks Wolfgang for helping out.

I am sending this info to my team members for review.

Regards,

Rajesh.

0 · Share

Database Queries Not Segregated (DB Tuning)

2 Replies

Your answer

Welcome to the
Dynatrace Community Forums

EMEA Community Member of the Month - November 2018

LATAM Community Member of the Month - November 2018

Follow this Question

Forum Tags

Database Queries Not Segregated (DB Tuning)

2 Replies

Your answer

Welcome to the Dynatrace Community Forums

EMEA Community Member of the Month - November 2018

LATAM Community Member of the Month - November 2018

Follow this Question

Forum Tags

Welcome to the
Dynatrace Community Forums