I am having problems using the SET QUERY_BAND via ODBC. I need to use it followed by a SELECT statement in a production context. I am not at liberty to change the SQL code nor post the actual code, but I have created a very basic equivalent to illustrate the problem.
If I use the following code
SET QUERY_BAND='pattern=PR%;' UPDATE FOR SESSION;
SELECT COUNT(*) FROM DBC.TABLESV
WHERE TABLENAME LIKE GETQUERYBANDVALUE(0, 'pattern');
then it works fine in Teradata SQL Assistant, but chokes in ODBC with the message "Only an ET or null statement is legal after a DDL Statement". OK, fine, whatever, I then changed the code to the following
BEGIN TRANSACTION;
SET QUERY_BAND='pattern=PR%;' FOR TRANSACTION;
SELECT COUNT(*) FROM DBC.TABLESV
WHERE TABLENAME LIKE GETQUERYBANDVALUE(0, 'pattern');
END TRANSACTION;
Again, works fine in Teradata SQL Assistant but when using it via ODBC I get the message "SET QUERY_BAND for TRANSACTION must be the first statement in a multi-statement request". Which is baffling me. Is anyone able to help me out here?
Forums: