BIDA ETL has long had the feature where the pipe character is inserted into the SQL Statement to denote a new line. This means that it is possible to re-create the statement changing the pipe character back to the newline when checking to see what statement is in the statements table. It has been a very handy feature over the years.
However, when sending sql into Meta5 we must remove the pipes as well as the comments. Meta5 receives an SQL statement and sends it unchanged to the ODBC connection specified. So what is in the statement in the statements table will go to the ODBC connection and pipes are not allowed.
So we have introduced a new feature to set the pipes as new line on or off.
This feature is in the processing page and is called:
LOAD SQL STATEMENTS WITH PIPE AS NEWLINE
It will default to Yes.
So when loading SQL Statements to be processed by Meta5 this processing parameter must be present and must be set to “No”.
We hope you like this new feature!
.