Archives of the TeradataForum
Message Posted: Wed, 17 Jul 2002 @ 19:41:21 GMT
It is my guess that you read about the ; trick but didn't notice that it was only a trick in BTEQ. The ODBC only see the commands as individual, not necessarily related commands.
If you wish the commands to act as a single transaction, the easiest and safest technique is to put them into a macro.
Otherwise, you are required to use the BT and ET commands to bracket them as a transaction. However, if an error occurs, the transaction ends and a new transaction starts. So, unless you have the ability to check the status code after every SQL statement, this is not a good solution.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|