Generally speaking, in the absence of any other memory pressure, a low procedure cache hit ratio means that when the DBMS goes to see if that statement has run previously and doesn't need to be parsed again, it doesn't find it in cache. This places more overhead on the DBMS because it then has to parse the statement, generate and optimized query plan, etc. Likely reasons for this are non-parameterized SQL statements (using literals that keep changing) or a LOT of ad hoc queries.
If the queries are using lots of literals, work with developers or third party application support to see if they might consider refactoring using parameters.
If i set "
optimize for ad hoc workloads" to True. Is there any help?