Archives of the TeradataForum
Message Posted: Thu, 09 Jan 2003 @ 18:28:22 GMT
| Subj: || || Re: Session Mode (ANSI v Teradata) |
| From: || || Hough, David A |
We ran ANSI as the default on one of our system for several years, but recently switched it back to Teradata. The ANSI transaction model
is vulnerable to accidental deadlock problems caused by users who forget to enter COMMIT WORK after a table update, and then walk away from
their terminals. We saw any number of odd ANSI vs Teradata performance issues, where one version ran 10-100X faster than the other
(RECAHWD38 & others). The system upgrade tools assume the system is in Teradata mode, and we into problems there (patching the upgrade
scripts is a scary business).
If it were my decision, I'd put the system in Teradata mode by default and then override the mode for specific connections if there where
some benefit to be gained. You can do this via the ODBC administrator by selecting Options and then setting the session mode to ANSI
(setting is hidden because the box is too small; scroll it up (RECA2Y34G)). Or you can set it in the connect string.