Submit Your Suggestions for Vista

When setting up a VA Notifier in the FROM WHERE field, the following conditions trigger an error:

• If you have a @ symbol in the field AND

• If there is a subquery with "GROUP BY" in it for a JOIN.

Your stored procedure dbo.vspVAWDTestQuery does not take the above condition into consideration. If it sees a @ symbol it then looks for "GROUP BY" and does some truncating, completely ignoring the idea that someone might have a GROUP BY within a subquery in a join, not just at the very bottom.

Why would it be useful to have a JOIN with a GROUP BY within it? It makes summarizing (or finding the last row of a thing) much easier. In my case, the last status update from a log.

I realize the goal of the TESTQUERY is to validate the SQL. With that in mind, are you aware of the following command?

sp_describe_first_result_set

https://learn.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-describe-first-result-set-transact-sql?view=sql-server-ver16

(Link above is just a link to Microsoft's page on the command).

Instead of hunting around for WHERE based on if @ does or does not exist, how about:

• Get all the variable names together

• Pass them to the procedure above.

This would remove your need to do truncating or searching for the WHERE clause.

This way it does not matter if any code is commented out, and it leaves ALL the SQL parsing to the engine. The only code you'd have to think about is how to detect the @names to build to pass to the procedure.

Please give this some thought.

Thanks.