SQL bind values filled with asterix " * "

Question

Question by Dennis M. · Feb 23, 2015 at 11:38 PM ·

SQL bind values filled with asterix " * "

Hi,

Any idea why for the most SQL statements I see bind values but for some I have only " * " (asterix)? While I can imagine that for some bind values this might be ok due to the fact that it is binary data, I dont understand that for others... any idea? (since I see a lot of bind values already, I can assume configuration is correct?!)

Best regards,
Dennis

1

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Answer 1 · 2015-02-23T23:52:43Z

Answer by Ahmed E. · Feb 23, 2015 at 11:52 PM

Dennis, do you have a screenshot of this?

Ahmed

0 Show 6 · Share

10 |2000000 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

Dennis M. · Feb 24, 2015 at 12:58 AM 0

Share

Hi Ahmed,

No, I dont unfortunately. Restricted customer access.

Best regards,
Dennis

Ahmed E. Dennis M. · Feb 24, 2015 at 01:15 AM 0

Share

I assume you already enabled capturing bind values in the sensor configuration. Did you also check if the privacy settings are masking the bind values? Settings > dynaTrace Server > Settings > Confidential Strings

Ahmed

Dennis M. Ahmed E. · Feb 24, 2015 at 01:25 AM 0

Share

Hi Ahmed,

Thanks, I checked the server settings. It was activated there. However, strange that I see it for some and for some not. Also, the description for these server settings say, that it is for setting confidential strings when "exporting a session". However, I was looking at live data.

Best regards,
Dennis

Ahmed E. Dennis M. · Feb 24, 2015 at 01:55 AM 0

Share

Dennis, which Dyntrace AM version is used there? I think that the Confidential String setting also applies to live data as per the Hint: "This will apply to live / stored sessions and to dashboards where the user does not have permissions to see the values."

It is indeed strange that you see the bind values for some statements and do not see them for others. Is there any difference in DB platform or character encoding that might cause this?

Rick B. Ahmed E. · Feb 24, 2015 at 03:55 AM 0

Share

Is it that you either see asterisks or "preparation"? We put "preparation" to differentiate between executed and prepared statements, this wouldn't be censored out as with other confidential strings if your user doesn't have the permission "Read Confidential Strings"

Rick B

Dennis M. Rick B. · Feb 24, 2015 at 07:31 PM 0

Share

Thanks for all your replies.. I saw preparation as well after I unchecked the checkbox for the setting Ahmed mentioned. As I saw some values, I dont think it's the rights of the user. It is dynatrace 6.0.0.7153. I thought maybe it is the way binary data is displayed?!

SQL bind values filled with asterix " * "

1 Reply

Join the conversation!

NAM 2019 SP3 is available

LIVE WEBINAR

Follow this Question

Forum Tags