Teradata provides the SQL Flagger to help users identify non-standard SQL. SQL Flagger permits statements flagged as non-entry-level or non-compliant ANSI/ISO SQL to run. Its task is to return a warning message to the requestor noting the noncompliance.
Flagging is enabled by a client application before a session is logged on and is used to assist in checking for ANSI compliance in code that must be portable across multiple vendor environments.
The SQL Flagger is disabled by default. You can enable or disable SQL Flagger using any of the following procedures, depending on your application.
| Application | Command or Option | Effect |
|---|---|---|
| BTEQ | .[SET] SESSION SQLFLAG ENTRY | Sets SQL Flagger to entry-level ANSI. |
| .[SET] SESSION SQLFLAG NONE | Turns off SQL Flagger. | |
| See Basic Teradata® Query Reference, B035-2414. | ||
| Preprocessor2 | SQLFLAGGER (ENTRY) | Sets SQL Flagger to entry-level ANSI. |
| SQLFLAGGER (NONE) | Turns off SQL Flagger. | |
| See Teradata® Preprocessor2 for Embedded SQL Programmer Guide, B035-2446. | ||
| CLI | set lang_conformance = '2' set lang_conformance to '2' |
Sets SQL Flagger to entry-level ANSI. |
| set lang_conformance = 'N' | Turns off SQL Flagger. | |
| See Teradata® Call-Level Interface Version 2 Reference for Mainframe-Attached Systems, B035-2417 and Teradata® Call-Level Interface Version 2 Reference for Workstation-Attached Systems, B035-2418. | ||