Can someone let me know the difference between Teradata Session mode and ANSI Session mode..What kind of impact does each mode have? Would like to specifically know about any issues with table creation..
There are two main areas of differences between Teradata and ANSI session modes.
The first (and arguably the most important) is to do with transaction control. This affects when a transaction starts, when it ends and what gets rolled back in the event of failure.
The second area is to do with defaults, some of which affect creating tables.
In a Teradata system, a table can be either MULTISET or SET. A MULTISET table (assuming no unque indexes are defined on it) allows duplicate rows to be stored in the table. A SET table (even if there are no unique indexes defined on it) will NOT allow duplicate rows to be stored. For a SET table, the DBMS will ensure that there are no duplicate rows. If the table is created when running in an ANSI session, the default table type is MULTISET, if created in Teradata mode the default is SET.
Does that help ?
Ward Analytics Ltd - information in motion www: http://www.ward-analytics.com
TERADATA MODE / ANSI MODE =========================================================================================== Comparison are NOT CASE Specific / Comparison ARE CASE Specific ALLOWS Tuncation of Display data / NO Tuncation of Display data CREATE TABLE default to SET tables / CREATE TABLE default to MULTISET tables Each Transaction is IMPLICIT automatically / Each Transaction is EXPLICIT automatically BTET (Begin and End Transaction) / BTEQ (no Begin and End Transaction necess.)