topic Re: Turn off capturing of DB Prepare statements in Open Q&A

Turn off capturing of DB Prepare statements

gilgi — Thu, 25 Jun 2026 07:57:14 GMT

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.

Re: Turn off capturing of DB Prepare statements

AravindhanV — Fri, 17 Jul 2026 05:32:17 GMT

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

Re: Turn off capturing of DB Prepare statements

dylan_taelemans — Fri, 17 Jul 2026 07:27:45 GMT

If you're using Dynatrace SaaS, you could try using OpenPipeline to drop them.

Something similar to this:

Re: Turn off capturing of DB Prepare statements

gilgi — Tue, 28 Jul 2026 05:51:56 GMT

Hi,

@AravindhanV this makes a lot of sense. we'll test it.

@dylan_taelemans while this will remove the spans, I suspect it will not affect the ingest & process ( as pipelines runs after this stage), hence will only solve storage but not the ingest quota.

Gil.

Re: Turn off capturing of DB Prepare statements

luiz_portela — Mon, 31 Aug 2026 16:14:47 GMT

@gilgi Did you figured this out?

SQL Prepare Statements are consuming right now 105% of our trace licensing.

The option "Capture SQL Bind values" is already disabled for us.

Re: Turn off capturing of DB Prepare statements

gilgi — Tue, 08 Sep 2026 06:00:11 GMT

Hi,

There was a thought that capture bind variables is causing that. it seems like its not. unfortunately we don't have any solution to that.

Seems like something Dynatrace team needs to answer or provide a way to resolve. It could be that using OTEL will reduce that but this means the OneAgent is loosing from its added value and more and more "manual" involvement, even if its not direct code change, will be required, hence making the deployment more comlicated and slower.