25 Jun 2026 08:57 AM
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.
17 Jul 2026 06:32 AM
Hi @gilgi ,
Its Valid question, how about using the Bind Variables,
Understanding would be, Bind variables allow the database server to prepare the statement once and execute it multiple times without reparsing or reanalyzing it.
Settings > Server-side service monitoring > Deep monitoring
Under Database Capture SQL bind values.
Have a look and share your thought
Thanks
17 Jul 2026 08:27 AM
If you're using Dynatrace SaaS, you could try using OpenPipeline to drop them.
Something similar to this:
Featured Posts