SQL Parsing: Prioritize nested FROM dbo.spStoredProcedure from compound statement

[rdhar]

trafficstars

Description

For nested/compound SQL statements, these are reported as "other" instead of the DB name called. This follows on from @elucus's #224 that was resolved by @nr-ahemsath in #370, and has been greatly appreciated by my organization as we can finally see most calls reporting to the actual table (thank you!).

Expected Behaviour

For example, here's one of our real examples which reports as "other" instead of "dbo.spStoredProcedure".

SET NOCOUNT ON; SET CONTEXT_INFO @ContextInfo; WITH T AS (SELECT [Status], row_number() over (ORDER BY [Description] asc) as row_asc FROM dbo.spStoredProcedure WHERE [Status] = @0), TWithRow as (SELECT *, row_number() over (ORDER BY row_asc DESC) as row_dsc FROM T) SELECT * FROM TWithRow WHERE row_asc between @MinRow and @MaxRow;

Additional Context

This was discovered with .NET agent v8.39.2.0. Happy to share more details about our environment, as required.

Thank you for your time.

[tehbio]

Hey @rdhar, thanks for report!

It does seem like the Agent could feasibly support these WITH CTE commands, instead pulling out the query itself to parse that, though it will take a little doing on our part.

I've added this to our backlog - I'd advise anyone interested in this feature giving it a 👍 to help us prioritize it accordingly!

[rdhar]

Thanks for the follow-up, @tehbio, I wasn't aware that common_table_expression could help support parsing of these kinds of queries. 👍

[workato-integration[bot]]

https://issues.newrelic.com/browse/NEWRELIC-8441

[workato-integration[bot]]

This issue won't be actioned.