Hi,
While Database prepare statements may be beneficial, I've seen more than once situations in which the DB prepare statements (in an intensive database based application) take a huge percentage of the allowed trace ingest quota for the V3 platform. This results in a customers missing out crucial spans and having to pay for additional storage because of spans they do not want.
My question to you: did you face such situations? how did you handle that? and for the Dynatrace guys our here - do you know of any way to just turn off the prepare statements collection?
Gil.
