Hello,
As per below screenshots, it says the parses are equal to no. of executions. is it referring to hard parse or soft parse?
how can we try to reduce the memory/cpu wait which is huge for this particular query
Hello,
As per below screenshots, it says the parses are equal to no. of executions. is it referring to hard parse or soft parse?
how can we try to reduce the memory/cpu wait which is huge for this particular query
Full Table Scan - as the DPA Advice says, probably first thing to look at is whether there are any suitable indexes? If so, are the table and index statistics up to date?
If not, can you add a new index or modify an existing index?
Can the SQL be re-written to be more efficient?
Have you checked the execution plan?
It doesn't seem to be bringing lots of data back, so the inefficiency of scanning the entire table to return 1-2 rows per execution is going to be costly (even though it averages about 0.4 seconds per execution).
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.