Example 1: Setting the quoting rules to SQL99

    SQL> SET QUOTING RULES 'SQL99';
    SQL> --
    SQL> -- SQL interprets double quotation marks as delimited identifiers.
    SQL> --
    SQL> CREATE TABLE "Employees_Table"
    cont>  ("Employee_ID" CHAR(6),
    cont>    "Employee_Name" CHAR (30));
    SQL> --
    SQL> -- SQL retains the upper- and lowercase letters within the identifier.
    SQL> --
    SQL> SHOW TABLE EMPLOYEES_TABLE
    No tables found
    SQL> SHOW TABLE "Employees_Table"
    Information for table Employees_Table

    Columns for table Employees_Table:
    Column Name                     Data Type        Domain
    -----------                     ---------        ------
    Employee_ID                     CHAR(6)
    Employee_Name                   CHAR(30)

       .
       .
       .

    Example 2: Setting the quoting rules to SQLV40

    SQL> SET QUOTING RULES 'SQLV40';
    SQL> --
    SQL> -- When you set the quoting rules to SQLV40, SQL interprets double
    SQL> -- quotation marks as string literals.
    SQL> --
    SQL> CREATE TABLE "Employees_Table"
    %SQL-I-DEPR_FEATURE, Deprecated Feature: " used instead of ' for string
    literal
    CREATE TABLE "Employees_Table"
                  ^
    %SQL-W-LOOK_FOR_STT, Syntax error, looking for:
    %SQL-W-LOOK_FOR_CON,            name, FROM,
    %SQL-F-LOOK_FOR_FIN,    found Employees_Table instead
    SQL> --
    SQL> -- Although you can use double quotation marks for string literals, SQL
    SQL> -- returns a deprecated feature message.
    SQL> --
    SQL> INSERT INTO EMPLOYEES
    cont>       (EMPLOYEE_ID, LAST_NAME, STATUS_CODE)
    cont> VALUES
    cont>       ("00500", 'Toliver', '1');
    %SQL-I-DEPR_FEATURE, Deprecated Feature: " used instead of ' for string
    literal
    1 row inserted
    SQL> --