SQL compliance

Last updated

SQL Compliance means adhering to rules laid for SQL. Some standards and protocols related to SQL are mentioned in this.

Contents

FunctionDescription Firebird IBM Db2 Oracle Database Microsoft SQL MonetDB MySQL PostgreSQL SQLite Apache Ignite Mimer SQL NexusDB
E011Numeric data typesPartialYesYesUn­knownYesUn­knownYesUn­knownPartialYesYes
E011-01INTEGER and SMALLINT data types (including all spellings)YesYesYesUn­knownYesYesYesUn­knownYesYesYes
E011-02REAL, DOUBLE PRECISION, and FLOAT data typesYesYesYesUn­knownYesUn­knownYesUn­knownYesYesYes
E011-03DECIMAL and NUMERIC data typesPartialYesYesUn­knownYesUn­knownYesUn­knownPartialYesYes
E011-04Arithmetic operatorsYesYesYesUn­knownYesUn­knownYesUn­knownPartialYesYes
E011-05Numeric comparisonYesYesYesUn­knownYesUn­knownYesUn­knownYesYesYes
E011-06Implicit casting among the numeric data typesYesYesYesUn­knownYesUn­knownYesUn­knownYesYesYes
E021Character string typesYesYesPartialPartialPartialUn­knownPartialUn­knownPartialYesYes
E021-01CHARACTER data type (including all its spellings)YesYesYesUn­knownYesUn­knownYesUn­knownPartialYesYes
E021-02CHARACTER VARYING data type (including all its spellings)YesYesPartialUn­knownYesUn­knownYesUn­knownPartialYesYes
E021-03Character literalsYesYesPartialUn­knownYesUn­knownYesUn­knownYesYesYes
E021-04CHARACTER_LENGTH functionYesYesNoNoYesYesPartial [note 1] NoYesYesYes
E021-05OCTET_LENGTH functionYesYesNoNoYesYesYesNo [note 2] YesYesYes
E021-06SUBSTRING functionYesYesNoNoYesYesYesNoYesYesYes
E021-07Character concatenationYesYesYesNoYesNoYesYesYesYesYes
E021-08UPPER and LOWER functionsYesYesYesYesYesYesYesYesYesYesYes
E021-09TRIM functionYesYesYesNo [note 3] [1] YesYesYesNoYesYesYes
E021-10Implicit casting among the fixed-length and variable-length character string typesYesYesYesUn­knownYesUn­knownYesUn­knownYesYesYes
E021-11POSITION functionYesYesNo [note 4] No [note 5] [2] No [note 6] YesYesNoYesYesYes
E021-12Character comparisonYesYesPartialUn­knownYesUn­knownYesUn­knownYesYesYes
E031IdentifiersYesYesPartialUn­knownYesUn­knownYesUn­knownYesYesYes
E031-01Delimited identifiersYesYesYesYesYesUn­knownYesYesYesYesYes
E031-02Lower case identifiersYesYesUn­knownUn­knownYesUn­knownYesUn­knownYesYesYes
E031-03Trailing underscoreYesYesYesYesYesYesYesYesYesYesYes
E051Basic query specificationPartialYesPartialUn­knownYesPartialYesUn­knownPartialYesYes
E051-01SELECT DISTINCTYesYesYesYesYesYesYesYesYesYesYes
E051-02GROUP BY clauseYesYesYesYesYesYesYesYesPartialYesYes
E051-04GROUP BY can contain columns not in <select-list>YesYesYesUn­knownYesNoYesUn­knownYesYesYes
E051-05Select list items can be renamedYesYesYesYesYesYesYesUn­knownYesYesYes
E051-06HAVING clauseYesYesYesYesYesYesYesUn­knownYesYesYes
E051-07Qualified * in select listYesYesYesUn­knownYesUn­knownYesUn­knownYesYesYes
E051-08Correlation names in the FROM clauseYesYesPartialUn­knownYesUn­knownYesUn­knownYesYesYes
E051-09Rename columns in the FROM clauseNoYesUn­knownUn­knownYesUn­knownYesUn­knownNoYesYes
E061Basic predicates and search conditionsYesPartialPartialUn­knownYesUn­knownYesUn­knownPartialYesYes
E061-01Comparison predicateYesYesPartialUn­knownYesUn­knownYesUn­knownYesYesYes
E061-02BETWEEN predicateYesYesPartialYesYesYesYesUn­knownYesYesYes
E061-03IN predicate with list of valuesYesYesPartialYesYesYesYesUn­knownYesYesYes
E061-04LIKE predicateYesYesPartialYesYesYesYesUn­knownPartialYesYes
E061-05LIKE predicate: ESCAPE clauseYesYesPartialUn­knownYesUn­knownYesUn­knownPartialYesYes
E061-06NULL predicateYesYesPartialUn­knownYesUn­knownYesUn­knownYesYesYes
E061-07Quantified comparison predicateYesYesPartialUn­knownYesUn­knownYesUn­knownPartialYesYes
E061-08EXISTS predicateYesYesPartialYesYesYesYesUn­knownYesYesYes
E061-09Subqueries in comparison predicateYesYesPartialUn­knownYesUn­knownYesUn­knownYesYesYes
E061-11Subqueries in IN predicateYesYesPartialYesYesYesYesUn­knownYesYesYes
E061-12Subqueries in quantified comparison predicateYesYesPartialUn­knownYesUn­knownYesUn­knownNoYesYes
E061-13Correlated subqueriesYesYesPartialYesYesUn­knownYesUn­knownYesYesYes
E061-14Search conditionYesPartial [note 7] PartialUn­knownYesUn­knownYesUn­knownYesYesYes
E071Basic query expressionsPartialYesPartialUn­knownYesUn­knownYesUn­knownYesYesYes
E071-01UNION DISTINCT table operatorYesYes [note 8] YesUn­knownYesUn­knownYesUn­knownYesYesYes
E071-02UNION ALL table operatorYesYesYesYesYesYesYesUn­knownYesYesYes
E071-03EXCEPT DISTINCT table operatorNoYes [note 8] No [note 9] Un­knownYesUn­knownYesUn­knownYesYesYes
E071-05Columns combined via table operators need not have exactly the same data typeYesYesYesYesYesUn­knownYesUn­knownYesYesYes
E071-06Table operators in subqueriesYesYesYesUn­knownYesUn­knownYesUn­knownYesYesYes
E081Basic PrivilegesYesYesPartialUn­knownPartialUn­knownYesUn­knownUn­knownYesNo
E081-01SELECT privilege at the table levelYesYesYesUn­knownYesUn­knownYesUn­knownUn­knownYesNo
E081-02DELETE privilegeYesYesYesUn­knownYesUn­knownYesUn­knownUn­knownYesNo
E081-03INSERT privilege at the table levelYesYesYesUn­knownYesUn­knownYesUn­knownUn­knownYesNo
E081-04UPDATE privilege at the table levelYesYesYesUn­knownYesUn­knownYesUn­knownUn­knownYesNo
E081-05UPDATE privilege at the column levelYesYesYesUn­knownYesUn­knownYesUn­knownUn­knownYesNo
E081-06REFERENCES privilege at the table levelYesYesYesUn­knownYesUn­knownYesUn­knownUn­knownYesNo
E081-07REFERENCES privilege at the column levelYesYesYesUn­knownYesUn­knownYesUn­knownUn­knownYesNo
E081-08WITH GRANT OPTIONYesYesYesUn­knownYesUn­knownYesUn­knownUn­knownYesNo
E081-09USAGE privilegeYesYesNoUn­knownNoUn­knownYesUn­knownUn­knownYesNo
E081-10EXECUTE privilegeYesYesYesUn­knownYesUn­knownYesUn­knownUn­knownYesNo
E091Set functionsYesYesYesUn­knownYesUn­knownYesUn­knownPartialYesYes
E091-01AVGYesYesYesYesYesYesYesYesYesYesYes
E091-02COUNTYesYesYesYesYesYesYesYesYesYesYes
E091-03MAXYesYesYesYesYesYesYesYesYesYesYes
E091-04MINYesYesYesYesYesYesYesYesYesYesYes
E091-05SUMYesYesYesYesYesYesYesYesYesYesYes
E091-06ALL quantifierYesYesYesUn­knownYesUn­knownYesUn­knownYesYesYes
E091-07DISTINCT quantifierYesYesYesYesYesYesYesUn­knownYesYesYes
E101Basic data manipulationYesYesYesUn­knownYesUn­knownYesPartialPartialYesYes
E101-01INSERT statementYesYesYesYesYesYesYesUn­knownPartialYesYes
E101-03Searched UPDATE statementYesYesYesUn­knownYesUn­knownYesUn­knownYesYesYes
E101-04Searched DELETE statementYesYesYesUn­knownYesUn­knownYesUn­knownYesYesYes
E111Single row SELECT statementYesYesYesUn­knownYesUn­knownYesUn­knownUn­knownYesYes
E121Basic cursor supportPartialYesPartialUn­knownNoUn­knownYesPartialNoYesYes
E121-01DECLARE CURSORYesYesPartialUn­knownNoUn­knownYesNoNoYesYes
E121-02ORDER BY columns need not be in select listYesYesYesYesYesYesYesYes [note 10] NoYesYes
E121-03Value expressions in ORDER BY clauseYesYesYesYesYesYesYesUn­knownNoYesYes
E121-04OPEN statementYesYesYesUn­knownNoUn­knownYesUn­knownNoYesYes
E121-06Positioned UPDATE statementYesYesYesUn­knownNoUn­knownYesUn­knownNoYesNo
E121-07Positioned DELETE statementYesYesYesUn­knownNoUn­knownYesUn­knownNoYesNo
E121-08CLOSE statementYesYesYesUn­knownNoUn­knownYesUn­knownNoYesYes
E121-10FETCH statement: implicit NEXTYesYesPartialUn­knownNoUn­knownYesUn­knownNoYesYes
E121-17WITH HOLD cursorsNoYesUn­knownUn­knownNoUn­knownYesUn­knownNoYesNo
E131Null value support (nulls in lieu of values)YesYesUn­knownYesYesYesYesUn­knownYesYesYes
E141Basic integrity constraintsPartialYesYesUn­knownPartialUn­knownYesPartialPartialYesYes
E141-01NOT NULL constraintsYesYesYesYesYesYesYesYesYesYesYes
E141-02UNIQUE constraints of NOT NULL columnsYesYesYesUn­knownYesUn­knownYesYesNoYesYes
E141-03PRIMARY KEY constraintsYesYesYesYesYesYesYesYes [note 11] PartialYesYes
E141-04Basic FOREIGN KEY constraint with the NO ACTION default for both referential delete action and referential update actionYesYesYesUn­knownYesUn­knownYesUn­knownNoYesYes
E141-06CHECK constraintsYesYesYesUn­knownNoUn­knownYesUn­knownNoYesYes
E141-07Column defaultsYesYesYesYesYesYesYesUn­knownNoYesYes
E141-08NOT NULL inferred on PRIMARY KEYYesYesYesUn­knownYesUn­knownYesPartial [note 12] PartialYesYes
E141-10Names in a foreign key can be specified in any orderNoYesYesUn­knownNoUn­knownYesUn­knownNoYesYes
E151Transaction supportPartialPartialYesYesYesUn­knownYesPartialNoYesYes
E151-01COMMIT statementYesYesYesYesYesUn­knownYesYesNoYesYes
E151-02ROLLBACK statementYesYesYesYesYesUn­knownYesYesNoYesYes
E152Basic SET TRANSACTION statementPartialYesYesUn­knownYesUn­knownYesNoNoYesPartial
E152-01SET TRANSACTION statement: ISOLATION LEVEL SERIALIZABLE clauseNoPartial [note 13] YesUn­knownYesUn­knownYesUn­knownNoYesPartial
E152-02SET TRANSACTION statement: READ ONLY and READ WRITE clausesYesNoYesUn­knownYesUn­knownYesUn­knownNoYesPartial
E*OtherPartialPartialPartialUn­knownYesUn­knownPartialUn­knownUn­knownYesPartial
E153Updatable queries with subqueriesYesYesYesUn­knownYesUn­knownYesUn­knownYesYesYes
E161SQL comments using leading double minusYesYesYesYesYesYesYesYesYesYesYes
E171SQLSTATE supportPartialYesYesUn­knownYesUn­knownYesUn­knownPartialYesNo
E182Host language binding (previously "Module Language")NoPartial [note 14] Un­knownUn­knownYesUn­knownNoUn­knownNoYes
F021Basic information schemaNoPartialNoYesNoYes [note 15] YesNoNoYes
F021-01COLUMNS viewNoPartial [note 16] NoYesNoYes [note 17] YesNo [note 18] NoYes
F021-02TABLES viewNoPartial [note 16] NoYesNoYes [note 17] YesNo [note 18] NoYes
F021-03VIEWS viewNoPartial [note 16] NoYesNoYes [note 17] YesNo [note 18] NoYes
F021-04TABLE_CONSTRAINTS viewNoPartial [note 16] NoYesNoYesYesNoNoYes
F021-05REFERENTIAL_CONSTRAINTS viewNoPartial [note 16] NoYesNoYesYesNoNoYes
F021-06CHECK_CONSTRAINTS viewNoPartial [note 16] NoYesNoYesYesNoNoYes
F031Basic schema manipulationPartialPartialPartialUn­knownPartialUn­knownYesPartialPartialYes
F031-01CREATE TABLE statement to create persistent base tablesYesYesYesYesYesYesYesUn­knownYesYes
F031-02CREATE VIEW statementYesYesYesYesYesUn­knownYesYesNoYes
F031-03GRANT statementYesYesYesUn­knownYesUn­knownYesNoNoYes
F031-04ALTER TABLE statement: ADD COLUMN clauseYesYesUn­knownUn­knownYesYesYesUn­knownYesYes
F031-13DROP TABLE statement: RESTRICT clausePartialYesNoUn­knownYesUn­knownYesUn­knownNoYes
F031-16DROP VIEW statement: RESTRICT clauseUn­knownYesNoUn­knownYesUn­knownYesUn­knownNoYes
F031-19REVOKE statement: RESTRICT clausePartialNoNoUn­knownNoUn­knownYesUn­knownNoYes
F041Basic joined tableYesYesYesUn­knownYesUn­knownYesPartialYesYes
F041-01Inner join (but not necessarily the INNER keyword)YesYesYesYesYesYesYesYesYesYes
F041-02INNER keywordYesYesYesYesYesYesYesYesYesYes
F041-03LEFT OUTER JOINYesYesYesYesYesYesYesYesYesYes
F041-04RIGHT OUTER JOINYesYesYesYesYesYesYesNoYesYes
F041-05Outer joins can be nestedYesYesYesUn­knownYesUn­knownYesUn­knownYesYes
F041-07The inner table in a left or right outer join can also be used in an inner joinYesYesYesUn­knownYesUn­knownYesUn­knownYesYes
F041-08All comparison operators are supported (rather than just =)YesYesYesUn­knownYesUn­knownYesUn­knownYesYes
F051Basic date and timePartialPartialYesUn­knownYesUn­knownYesPartialPartialYes
F051-01DATE data type (including support of DATE literal)YesYesYesNoYesYesYesNoPartialYes
F051-02TIME data type (including support of TIME literal) with fractional seconds precision of at least 0YesYesNoUn­knownYesUn­knownYesUn­knownPartialYes
F051-03TIMESTAMP data type (including support of TIMESTAMP literal) with fractional seconds precision of at least 0 and 6YesYesYesUn­knownYesUn­knownYesUn­knownPartialYes
F051-04Comparison predicate on DATE, TIME, and TIMESTAMP data typesYesYesYesUn­knownYesUn­knownYesUn­knownYesYes
F051-05Explicit CAST between datetime types and character string typesYesYesYesUn­knownYesUn­knownYesPartialYesYes
F051-06CURRENT_DATEYesYesYesUn­knownYesYesYesYesYesYes
F051-07LOCALTIMEPartialNoNoUn­knownYesYesYesNoYesYes
F051-08LOCALTIMESTAMPPartialNoYesUn­knownYesYesYesNoYesYes
F081UNION and EXCEPT in viewsPartialYesUn­knownYesYesUn­knownYesYesNoYes
F131Grouped operationsYesUn­knownYesUn­knownYesUn­knownYesUn­knownNoYes
F131-01WHERE, GROUP BY, and HAVING clauses supported in queries with grouped viewsYesUn­knownYesUn­knownYesUn­knownYesUn­knownNoYes
F131-02Multiple tables supported in queries with grouped viewsYesUn­knownYesUn­knownYesUn­knownYesUn­knownNoYes
F131-03Set functions supported in queries with grouped viewsYesUn­knownYesUn­knownYesUn­knownYesUn­knownNoYes
F131-04Subqueries with GROUP BY and HAVING clauses and grouped viewsYesUn­knownYesUn­knownYesUn­knownYesUn­knownNoYes
F131-05Single row SELECT with GROUP BY and HAVING clauses and grouped viewsYesUn­knownYesUn­knownYesUn­knownYesUn­knownNoYes
F*OtherPartialUn­knownPartialUn­knownYesUn­knownPartialUn­knownPartialYes
F181Multiple module supportNoUn­knownYesUn­knownYesUn­knownNoUn­knownNoYes
F201CAST functionYesUn­knownYesUn­knownYesYesYesYesYesYes
F221Explicit defaultsNoUn­knownUn­knownUn­knownYesUn­knownYesUn­knownYesYes
F261CASE expressionYesUn­knownYesYesYesYesYesUn­knownYesYes
F261-01Simple CASEYesUn­knownYesUn­knownYesUn­knownYesUn­knownYesYes
F261-02Searched CASEYesUn­knownYesUn­knownYesUn­knownYesUn­knownYesYes
F261-03NULLIFYesUn­knownYesUn­knownYesUn­knownYesUn­knownYesYes
F261-04COALESCEYesUn­knownYesYesYesYesYesUn­knownYesYes
F311Schema definition statementNoUn­knownYesUn­knownPartialUn­knownYesPartialNoYes
F311-01CREATE SCHEMANoUn­knownYesUn­knownYesUn­knownYesNoNoYes
F311-02CREATE TABLE for persistent base tablesNoUn­knownYesYesYesYesYesUn­knownNoYes
F311-03CREATE VIEWNoUn­knownYesYesYesYesYesYesNoYes
F311-04CREATE VIEW: WITH CHECK OPTIONNoUn­knownYesUn­knownNoUn­knownYesUn­knownNoYes
F311-05GRANT statementNoUn­knownYesUn­knownYesUn­knownYesNoNoYes
F471Scalar subquery valuesYesUn­knownYesUn­knownYesUn­knownYesYesYesYes
F481Expanded NULL predicateYesUn­knownYesUn­knownYesUn­knownYesUn­knownYesYes
F501Features and conformance viewsUn­knownUn­knownNoNoNoUn­knownPartialUn­knownNoYes
F501-01SQL_FEATURES viewNoNoNoNoNoNoYesNoNoYes
F501-02SQL_SIZING viewUn­knownUn­knownNoNoNoUn­knownYesNoNoYes
F501-03SQL_LANGUAGES viewUn­knownUn­knownNoNoNoUn­knownYesNoNoYes
F812Basic flaggingNoUn­knownSQL-92Un­knownNoUn­knownNoUn­knownNoYes
S011Distinct data typesNoUn­knownUn­knownUn­knownNoUn­knownNoUn­knownNoYes
S011-01USER_DEFINED_TYPES viewUn­knownUn­knownUn­knownUn­knownNoUn­knownNoUn­knownNoYes
T321Basic SQL-invoked routinesPartialUn­knownPartialUn­knownPartialUn­knownPartialUn­knownNoYes
T321-01User-defined functions with no overloadingYesUn­knownUn­knownYesYesYesYesUn­knownNoYes
T321-02User-defined stored procedures with no overloadingYesUn­knownUn­knownYesYesUn­knownYesUn­knownNoYes
T321-03Function invocationYesUn­knownYesYesYesYesYesUn­knownNoYes
T321-04CALL statementPartialUn­knownYesUn­knownYesUn­knownYesNoNoYes
T321-05RETURN statementPartialUn­knownPartial [note 19] Un­knownYesUn­knownNoNoNoYes
T321-06ROUTINES viewUn­knownUn­knownNo [note 20] Un­knownNo [note 21] Un­knownYesUn­knownNoYes
T321-07PARAMETERS viewUn­knownUn­knownNo [note 22] Un­knownNo [note 23] Un­knownYesUn­knownNoYes
T631IN predicate with one list elementYesUn­knownYesUn­knownYesUn­knownYesUn­knownNoYes

Footnotes

  1. Trims trailing spaces from CHARACTER values before counting
  2. There is no built-in function by this name, although the number of octets in a string can be determined by using LENGTH(CAST(X AS BLOB)).
  3. There are LTRIM and RTRIM functions for equivalent functionality.
  4. There is INSTR.
  5. There is the CHARINDEX function for equivalent functionality.
  6. There is the charindex function for equivalent functionality.
  7. Lacks support for [IS [NOT] TRUE|FALSE|UNKNOWN]
  8. 1 2 Without DISTINCT keyword
  9. Use MINUS instead of EXCEPT DISTINCT
  10. Except compound queries.
  11. Only WITHOUT ROWID tables have real primary keys other than the rowid (INTEGER PRIMARY KEY)
  12. Only for WITHOUT ROWID tables.
  13. SET [CURRENT] ISOLATION used instead of SET TRANSACTION
  14. Supports embedded language features but not the specific MODULE syntax
  15. "MySQL :: MySQL 5.7 Reference Manual :: 24 INFORMATION_SCHEMA Tables".
  16. 1 2 3 4 5 6 Included in SYSIBM schema
  17. 1 2 3 Also includes MySQL-specific extension columns
  18. 1 2 3 You can use PRAGMA for obtaining this information, and can create an information schema based on this, but it is not build in.
  19. Oracle supports the following subfeature in PL/SQL but not in Oracle SQL.
  20. Use the ALL PROCEDURES metadata view.
  21. Use the sys.functions metadata view.
  22. Use the ALL_ARGUMENTS and ALL_METHOD_PARAMS metadata views.
  23. Use the sys.args metadata view.

See also

Related Research Articles

SQL is a domain-specific language used in programming and designed for managing data held in a relational database management system (RDBMS), or for stream processing in a relational data stream management system (RDSMS). It is particularly useful in handling structured data, i.e. data incorporating relations among entities and variables.

In computing, Open Database Connectivity (ODBC) is a standard application programming interface (API) for accessing database management systems (DBMS). The designers of ODBC aimed to make it independent of database systems and operating systems. An application written using ODBC can be ported to other platforms, both on the client and server side, with few changes to the data access code.

In the context of SQL, data definition or data description language (DDL) is a syntax for creating and modifying database objects such as tables, indices, and users. DDL statements are similar to a computer programming language for defining data structures, especially database schemas. Common examples of DDL statements include CREATE, ALTER, and DROP.

An SQL INSERT statement adds one or more records to any single table in a relational database.

<span class="mw-page-title-main">Physical schema</span> Representation of a data design

A physical data model is a representation of a data design as implemented, or intended to be implemented, in a database management system. In the lifecycle of a project it typically derives from a logical data model, though it may be reverse-engineered from a given database implementation. A complete physical data model will include all the database artifacts required to create relationships between tables or to achieve performance goals, such as indexes, constraint definitions, linking tables, partitioned tables or clusters. Analysts can usually use a physical data model to calculate storage estimates; it may include specific storage allocation details for a given database system.

A database trigger is procedural code that is automatically executed in response to certain events on a particular table or view in a database. The trigger is mostly used for maintaining the integrity of the information on the database. For example, when a new record is added to the employees table, new records should also be created in the tables of the taxes, vacations and salaries. Triggers can also be used to log historical data, for example to keep track of employees' previous salaries.

ADO.NET is a data access technology from the Microsoft .NET Framework that provides communication between relational and non-relational systems through a common set of components. ADO.NET is a set of computer software components that programmers can use to access data and data services from a database. It is a part of the base class library that is included with the Microsoft .NET Framework. It is commonly used by programmers to access and modify data stored in relational database systems, though it can also access data in non-relational data sources. ADO.NET is sometimes considered an evolution of ActiveX Data Objects (ADO) technology, but was changed so extensively that it can be considered an entirely new product.

The following tables compare general and technical information for a number of relational database management systems. Please see the individual products' articles for further information. Unless otherwise specified in footnotes, comparisons are based on the stable versions without any add-ons, extensions or external programs.

A table is a collection of related data held in a table format within a database. It consists of columns and rows.

In a database, a view is the result set of a stored query on the data, which the database users can query just as they would in a persistent database collection object. This pre-established query command is kept in the database dictionary. Unlike ordinary base tables in a relational database, a view does not form part of the physical schema: as a result set, it is a virtual table computed or collated dynamically from data in the database when access to that view is requested. Changes applied to the data in a relevant underlying table are reflected in the data shown in subsequent invocations of the view. In some NoSQL databases, views are the only way to query data.

Oracle Enterprise Manager (OEM) is a set of web-based tools aimed at managing software and hardware produced by Oracle Corporation as well as by some non-Oracle entities.

Set operations allow the results of multiple queries to be combined into a single result set. Set operators include UNION, INTERSECT, and EXCEPT.

Oracle Database provides information about all of the tables, views, columns, and procedures in a database. This information about information is known as metadata. It is stored in two locations: data dictionary tables and a metadata registry.

Entity–attribute–value model (EAV) is a data model to encode, in a space-efficient manner, entities where the number of attributes that can be used to describe them is potentially vast, but the number that will actually apply to a given entity is relatively modest. Such entities correspond to the mathematical notion of a sparse matrix.

In relational databases, the information schema is an ANSI-standard set of read-only views that provide information about all of the tables, views, columns, and procedures in a database. It can be used as a source of the information that some databases make available through non-standard commands, such as:

 => SELECT count(table_name) FROM information_schema.tables;  count   -------  99    => SELECT column_name, data_type, column_default, is_nullable  FROM information_schema.columns WHERE table_name='alpha';  column_name | data_type | column_default | is_nullable   -------------+-----------+----------------+-------------  foo | integer | | YES  bar | character | | YES    => SELECT * FROM information_schema.information_schema_catalog_name;  catalog_name   --------------  johnd  

The DUAL table is a special one-row, one-column table present by default in Oracle and other database installations. In Oracle, the table has a single VARCHAR2(1) column called DUMMY that has a value of 'X'. It is suitable for use in selecting a pseudo column such as SYSDATE or USER.

Microsoft SQL Server is a relational database management system developed by Microsoft. As a database server, it is a software product with the primary function of storing and retrieving data as requested by other software applications—which may run either on the same computer or on another computer across a network. Microsoft markets at least a dozen different editions of Microsoft SQL Server, aimed at different audiences and for workloads ranging from small single-machine applications to large Internet-facing applications with many concurrent users.

A hierarchical query is a type of SQL query that handles hierarchical model data. They are special cases of more general recursive fixpoint queries, which compute transitive closures.

<span class="mw-page-title-main">Apache Hive</span> Database engine

Apache Hive is a data warehouse software project built on top of Apache Hadoop for providing data query and analysis. Hive gives an SQL-like interface to query data stored in various databases and file systems that integrate with Hadoop. Traditional SQL queries must be implemented in the MapReduce Java API to execute SQL applications and queries over distributed data. Hive provides the necessary SQL abstraction to integrate SQL-like queries (HiveQL) into the underlying Java without the need to implement queries in the low-level Java API. Since most data warehousing applications work with SQL-based querying languages, Hive aids portability of SQL-based applications to Hadoop. While initially developed by Facebook, Apache Hive is used and developed by other companies such as Netflix and the Financial Industry Regulatory Authority (FINRA). Amazon maintains a software fork of Apache Hive included in Amazon Elastic MapReduce on Amazon Web Services.

<span class="mw-page-title-main">Database Workbench</span>

Database Workbench is a software application for development and administration of multiple relational databases using SQL, with interoperationality between different database systems, developed by Upscene Productions.

References

  1. "[MS-TSQLISO02]: E021-09, TRIM function". docs.microsoft.com. Retrieved 22 April 2020.
  2. "[MS-TSQLISO02]: E021-11, POSITION function". docs.microsoft.com. Retrieved 22 April 2020.