*** Error 3722 Only a COMMIT WORK or null statement is legal after a DDL Statement.
*** Failure 3932 Only an ET or null statement is legal after a DDL Statement.
.SET SESSION TRANSACTION ANSI
.SET SESSION TRANSACTION BTET
*** Error: You must not be logged on to change the SQLFLAG or TRANSACTION settings
|
Ansi Mode |
Teradata Mode |
Transactions / SQLs |
Explicit COMMIT statement is required to persist completed DMLs/transactions in database |
DMLs/transactions are autocommit implicitly |
Default Table creation |
MULTSET table will be created if not specified explicitly |
SET table will be created if not specified explicitly |
Default Character Comparison |
Data comparison is CASESPECIFIC |
Data comparison is not CASESPECIFIC |
Logoff |
Completed DMLs/transactions will not persist in database if logged off without commit |
Completed DMLs/transactions generally persist in database after logoff.
|
Character Truncation |
Normal truncation using CAST function will result in error. |
Normal truncation using CAST function will give truncated result with the specified length. |
Statements after DDL |
COMMIT must be the next statement after any DDL statement else statements will fail |
Generally any statement can be executed after DDL. But if DDL statement is executed within BT then ET must be next statement else statements will fail. |
BT(Begin Transaction) / ET(End Transaction) |
BT is not permitted |
BT can be used to stop implicitly committing every statement, once ET is issued then it will commit all the transactions. |