DUAL table

Oracle's SQL syntax requires the FROM clause but some queries don't require any tables - DUAL can be used in these cases.

SELECT 1+1
FROM dual;

SELECT 1 
FROM dual;

SELECT USER 
FROM dual;

SELECT SYSDATE 
FROM dual;

SELECT * 
FROM dual;

Charles Weiss explains why he created DUAL:

I created the DUAL table as an underlying object in the Oracle Data Dictionary. It was never meant to be seen itself, but instead used inside a view that was expected to be queried. The idea was that you could do a JOIN to the DUAL table and create two rows in the result for every one row in your table. Then, by using GROUP BY, the resulting join could be summarized to show the amount of storage for the DATA extent and for the INDEX extent(s). The name, DUAL, seemed apt for the process of creating a pair of rows from just one.[1]

Beginning with 10g Release 1, Oracle no longer performs physical or logical I/O on the DUAL table, though the table still exists.[2]

DUAL is readily available for all authorized users in a SQL database.

Several other databases (including Microsoft SQL Server, MySQL, PostgreSQL, SQLite, and Teradata) enable one to omit the FROM clause entirely if no table is needed. This avoids the need for any dummy table.

• ClickHouse has a one-row system table system.one with a single column named "dummy" of type UInt8 and value 0. This table is implicitly used when no table is specified in the SELECT query.
• Firebird has a one-row system table RDB$DATABASE that is used in the same way as Oracle's DUAL, although it also has a meaning of its own.
• IBM Db2 has a view that resolves DUAL when using Oracle Compatibility.[3] It also has a table called sysibm.sysdummy1 that has similar properties to the Oracle DUAL one.
• Informix: Informix version 11.50 and later has a table named sysmaster:"informix".sysdual with the same functionality but a more verbose name.[4] You can use CREATE PUBLIC SYNONYM dual FOR sysmaster:"informix".sysdual to create a name dual in the current database with the same functionality.
• Microsoft Access: A table named DUAL may be created and the single-row constraint enforced via ADO (Table-less UNION query in MS Access)
• Microsoft SQL Server: SQL Server does not require a dummy table. Queries like 'select 1 + 1' can be run without a "from" clause/table name.[5]
• MySQL allows DUAL to be specified as a table in queries that do not need data from any tables.[6] It is suitable for use in selecting a result function such as SYSDATE() or USER(), although it is not essential.
• PostgreSQL: A DUAL-view can be added to ease porting from Oracle.[7]
• Snowflake: DUAL is supported, but not explicitly documented. It appears in sample SQL for other operations in the documentation.
• SQLite: A VIEW named "dual" that works the same as the Oracle "dual" table can be created as follows: CREATE VIEW dual AS SELECT 'x' AS dummy;
• SAP HANA has a table called DUMMY that works the same as the Oracle "dual" table.
• Teradata database does not require a dummy table. Queries like 'select 1 + 1' can be run without a "from" clause/table name.
• Vertica has support for a DUAL table in their official documentation.[8]