Hi, I've got a filter that's performing a SQL Set Fields and the SQL is constructed using a Common Table Expression (i.e. it begins with a "WITH" keyword).
Through ARS logging and using SQL Server profiling, I can see that the SQL is being submitted to SQL Server and executed. If I run the SQL by hand in a SQL query window I can see that it does yield the expected results. However, the fields being set by the Set Fields are NOT being set to any of the result values, they're just being set to NULL. I'm a bit concerned that this might be a "security feature" that BMC's installed to prevent SQL injection or something. Has anyone else seen this behavior? Is there an easy workaround or fix? Yes, in this particular case I can probably refactor the SQL to eliminate the CTE, but for a few reasons this is not a convenient solution. FYI... SQL Server 2014 ARS v8.1.02 Thanks, Charlie
-- ARSList mailing list [email protected] https://mailman.rrr.se/cgi/listinfo/arslist
