-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removing the SQL command text from the dependency name for Framework #1723
Removing the SQL command text from the dependency name for Framework #1723
Conversation
…SQL processing to reduce event bloat.
Is this something that can be looked at @TimothyMothra? Don't know if I'm supposed to add a reviewer or if that's all on your end :) |
Hi @stebet ! |
/AzurePipelines run |
Azure Pipelines successfully started running 3 pipeline(s). |
@cijothomas I'm okay with this change. I just wanted to double-check with you... do you know if anything was dependent on this behavior? |
Thanks. The full sql text was supposed to be part of .Data only . Thanks for fixing this. |
/AzurePipelines run |
Azure Pipelines successfully started running 3 pipeline(s). |
Removing the SQL command text from the dependency name for Framework processing to reduce event bloat.
Changes
When using the Microsoft.Data.SqlClient NuGet package for SQL statements, which now provides the SQL Command Text, the SQL dependency telemetry are all bloated with the SQL Command text for ad-hoc queries when running under .NET Framework.
For comparison, the .NET Core SQL dependency collector does not use the command text in the dependency name, and just relies on the
Data
property to provide that information, so this should bring more parity between .NET Framework and .NET Core SQL dependencies, and reduce the amount of data sent when running under the .NET Framework and executing ad-hoc statements (like when using Entity Framework).Checklist