16.20 - Using the SQL Flagger - Teradata Database - Teradata Vantage NewSQL Engine

Teradata Vantage™ SQL Fundamentals

Product
Teradata Database
Teradata Vantage NewSQL Engine
Release Number
16.20
Published
March 2019
Language
English (United States)
Last Update
2019-05-02
dita:mapPath
zce1519094756513.ditamap
dita:ditavalPath
TD_DBS_16_20_Update1.ditaval

Teradata provides the SQL Flagger to help users identify non-standard SQL. SQL Flagger always permits statements flagged as non-entry-level or non-compliant ANSI/ISO SQL to execute. 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 generally is used only 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 it using any of the following procedures, depending on your application.

For this software … Use these commands or options … To turn the SQL Flagger …
BTEQ .[SET] SESSION SQLFLAG ENTRY to entry-level ANSI
.[SET] SESSION SQLFLAG NONE off
For details on using BTEQ commands, see Basic Teradata® Query Reference, B035-2414.
Preprocessor2 SQLFLAGGER(ENTRY) to entry-level ANSI
SQLFLAGGER(NONE) off
For details on setting Preprocessor options, see Teradata® Preprocessor2 for Embedded SQL Programmer Guide, B035-2446.
CLI set lang_conformance = ‘2’

set lang_conformance to ‘2’

to entry-level ANSI
set lang_conformance = ‘N’ off
For details on setting the conformance field, 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.