Handle TSQL commands in the dependency blade better
In the command field in the dependency blade, long TSQL commands get truncated and remove the most important part of the statement, the FROM and WHERE clauses. Without this, the entire blade is almost useless.
It would be better to show the entire statement, or even truncate the start of the statement, rather than the end.
Can you comment on how often you are hitting the length limitation issue in your use cases?
-AppInsights Product Management
Kristian Williams commented
The truncation happens very often with large Entity Framework queries. Especially ones which make extended use of the Include() method to condense sub-selects into a single query.
Robert Downey commented
We're working to improve this, but probably 20% of our queries exceed this limit - but, more importantly, 90% of our poorly performing queries do, and this is exactly what we want AI to help us diagnose.
Dan Kellett commented
It depends on the table column count and Linq to EF queries. In one of our application it happens to over at least 50% of queries. In cases where we are investigating slow requests, its usually a bad linq to ef query, so its closer to 100% during that situation. Which is what triggered this request.