Comparison_of_relational_database_management_systems

Comparison of relational database management systems

Comparison of relational database management systems

Add article description

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.

General information

More information Maintainer, First public release date ...

Operating system support

The operating systems that the RDBMSes can run on.

More information Windows, macOS ...

Fundamental features

Information about what fundamental RDBMS features are implemented natively.

More information Database Name, ACID ...
  • Note (1): Currently only supports read uncommitted transaction isolation. Version 1.9 adds serializable isolation and version 2.0 will be fully ACID compliant.
  • Note (2): MariaDB and MySQL provide ACID compliance through the default InnoDB storage engine.[71][72]
  • Note (3): "For other than InnoDB storage engines, MySQL Server parses and ignores the FOREIGN KEY and REFERENCES syntax in CREATE TABLE statements. The CHECK clause is parsed but ignored by all storage engines."[73]
  • Note (4): Support for Unicode is new in version 10.0.
  • Note (5): MySQL provides GUI interface through MySQL Workbench.
  • Note (6): OpenEdge SQL database engine uses Referential Integrity, OpenEdge ABL Database engine does not and is handled via database triggers.

Limits

Information about data size limits.

More information Max DB size, Max table size ...
  • Note (1): Firebird 2.x maximum database size is effectively unlimited with the largest known database size >980 GB.[79] Firebird 1.5.x maximum database size: 32 TB.
  • Note (2): Limit is 1038 using DECIMAL datatype.[80]
  • Note (3): InnoDB is limited to 8,000 bytes (excluding VARBINARY, VARCHAR, BLOB, or TEXT columns).[81]
  • Note (4): InnoDB is limited to 1,017 columns.[81]
  • Note (6): Using VARCHAR (MAX) in SQL 2005 and later.[82]
  • Note (7): When using a page size of 32 KB, and when BLOB/CLOB data is stored in the database file.
  • Note (8): Java array size limit of 2,147,483,648 (231) objects per array applies. This limit applies to number of characters in names, rows per table, columns per table, and characters per CHAR/VARCHAR.
  • Note (9): Despite the lack of a date datatype, SQLite does include date and time functions,[83] which work for timestamps between 24 November 4714 B.C. and 1 November 5352.
  • Note (10): Informix DATETIME type has adjustable range from YEAR only through 1/10000th second. DATETIME date range is 0001-01-01 00:00:00.00000 through 9999-12-31 23:59:59.99999.
  • Note (11): Since version 12c. Earlier versions support up to 4000 B.
  • Note (12): The 128 PB limit refers to the storage limit of a single Informix server instance. Informix v12.10 and later versions support using sharding techniques to distribute a table across multiple server instances. A distributed Informix database has no upper limit on table or database size.
  • Note (13): Informix DECIMAL type supports up to 32 decimal digits of precision with a range of 10−130 to 10125. Fixed and variable precision are supported.

Tables and views

Information about what tables and views (other than basic ones) are supported natively.

More information Temporary table, Materialized view ...

Note (1): Server provides tempdb, which can be used for public and private (for the session) temp tables.[84]

Note (2): Materialized views are not supported in Informix; the term is used in IBM's documentation to refer to a temporary table created to run the view's query when it is too complex, but one cannot for example define the way it is refreshed or build an index on it. The term is defined in the Informix Performance Guide.[85]

Note (4): Materialized views can be emulated using stored procedures and triggers.[86]

Indexes

Information about what indexes (other than basic B-/B+ tree indexes) are supported natively.

More information R-/R+ tree, Hash ...

Note (1): The users need to use a function from freeAdhocUDF library or similar.[121]

Note (2): Can be implemented for most data types using expression-based indexes.

Note (3): Can be emulated by indexing a computed column[122] (doesn't easily update) or by using an "Indexed View"[123] (proper name not just any view works[124]).

Note (4): Used for InMemory ColumnStore index, temporary hash index for hash join, Non/Cluster & fill factor.

Note (5): InnoDB automatically generates adaptive hash index[125] entries as needed.

Note (6): Can be implemented using Function-based Indexes in Oracle 8i and higher, but the function needs to be used in the sql for the index to be used.

Note (7): A PostgreSQL functional index can be used to reverse the order of a field.

Note (10): B+ tree and full-text only for now.

Note (11): R-Tree indexing available in base edition with Locator but some functionality requires Personal Edition or Enterprise Edition with Spatial option.

Database capabilities

More information Union, Intersect ...

Note (1): Recursive CTEs introduced in 11gR2 supersedes similar construct called CONNECT BY.

Data types

More information Type system, Integer ...

Other objects

Information about what other objects are supported natively.

More information Data Domain, Cursor ...

Note (1): Both function and procedure refer to internal routines written in SQL and/or procedural language like PL/SQL. External routine refers to the one written in the host languages, such as C, Java, Cobol, etc. "Stored procedure" is a commonly used term for these routine types. However, its definition varies between different database vendors.

Note (2): In Derby, H2, LucidDB, and CUBRID, users code functions and procedures in Java.

Note (3): ENUM datatype exists. CHECK clause is parsed, but not enforced in runtime.

Note (5): Informix supports external functions written in Java, C, & C++.

Partitioning

Information about what partitioning methods are supported natively.

More information Range, Hash ...

Access control

Information about access control functionalities.

More information Native network encryption1, Brute-force protection ...

Note (1): Network traffic could be transmitted in a secure way (not clear-text, in general SSL encryption). Precise if option is default, included option or an extra modules to buy.

Note (2): Options are present to set a minimum size for password, respect complexity like presence of numbers or special characters.

Note (3): How do you get security updates? Is it free access, do you need a login or to pay? Is there easy access through a Web/FTP portal or RSS feed or only through offline access (mail CD-ROM, phone).

Note (4): Does database process run as root/administrator or unprivileged user? What is default configuration?

Note (5): Is there a separate user to manage special operation like backup (only dump/restore permissions), security officer (audit), administrator (add user/create database), etc.? Is it default or optional?

Note (6): Common Criteria certified product list.[179]

Note (7): FirebirdSQL seems to only have SYSDBA user and DB owner. There are no separate roles for backup operator and security administrator.

Note (8): User can define a dedicated backup user but nothing particular in default install.[180]

Note (9): Authentication methods.[181]

Note (10): Informix Dynamic Server supports PAM and other configurable authentication. By default uses OS authentication.

Note (11): Authentication methods.[182]

Note (12): With the use of Pervasive AuditMaster.

Note (13): User-based security is optional in Polyhedra, but when enabled can be enhanced to a role-based model with auditing.[183]

Databases vs schemas (terminology)

The SQL specification defines what an "SQL schema" is; however, databases implement it differently. To compound this confusion the functionality can overlap with that of a parent database. An SQL schema is simply a namespace within a database; things within this namespace are addressed using the member operator dot ".". This seems to be a universal among all of the implementations.

A true fully (database, schema, and table) qualified query is exemplified as such: SELECT * FROM database.schema.table

Both a schema and a database can be used to isolate one table, "foo", from another like-named table "foo". The following is pseudo code:

  • SELECT * FROM database1.foo vs. SELECT * FROM database2.foo (no explicit schema between database and table)
  • SELECT * FROM [database1.]default.foo vs. SELECT * FROM [database1.]alternate.foo (no explicit database prefix)

The problem that arises is that former MySQL users will create multiple databases for one project. In this context, MySQL databases are analogous in function to PostgreSQL-schemas, insomuch as PostgreSQL deliberately lacks off-the-shelf cross-database functionality (preferring multi-tenancy) that MySQL has. Conversely, PostgreSQL has applied more of the specification implementing cross-table, cross-schema, and then left room for future cross-database functionality.

MySQL aliases schema with database behind the scenes, such that CREATE SCHEMA and CREATE DATABASE are analogs. It can therefore be said that MySQL has implemented cross-database functionality, skipped schema functionality entirely, and provided similar functionality into their implementation of a database. In summary, PostgreSQL fully supports schemas and multi-tenancy by strictly separating databases from each other and thus lacks some functionality MySQL has with databases, while MySQL does not even attempt to support standard schemas.

Oracle has its own spin where creating a user is synonymous with creating a schema. Thus a database administrator can create a user called PROJECT and then create a table PROJECT.TABLE. Users can exist without schema objects, but an object is always associated with an owner (though that owner may not have privileges to connect to the database). With the 'shared-everything' Oracle RAC architecture, the same database can be opened by multiple servers concurrently. This is independent of replication, which can also be used, whereby the data is copied for use by different servers. In the Oracle implementation, a 'database' is a set of files which contains the data while the 'instance' is a set of processes (and memory) through which a database is accessed.

Informix supports multiple databases in a server instance like MySQL. It supports the CREATE SCHEMA syntax as a way to group DDL statements into a single unit creating all objects created as a part of the schema as a single owner. Informix supports a database mode called ANSI mode which supports creating objects with the same name but owned by different users.

PostgreSQL and some other databases have support for foreign schemas, which is the ability to import schemas from other servers as defined in ISO/IEC 9075-9 (published as part of SQL:2008). This appears like any other schema in the database according to the SQL specification while accessing data stored either in a different database or a different server instance. The import can be made either as an entire foreign schema or merely certain tables belonging to that foreign schema.[184] While support for ISO/IEC 9075-9 bridges the gap between the two competing philosophies surrounding schemas, MySQL and Informix maintain an implicit association between databases while ISO/IEC 9075-9 requires that any such linkages be explicit in nature.

See also

References

  1. [1]
    "Product Release Life Cycle". 10 January 2020.
  2. [2]
    "Apache Derby: Downloads". Retrieved 2024-03-18.
  3. [3]
    Derby - ASF JIRA
  4. [4]
    cockroachdb Issue tracker
  5. [5]
    CUBRID / Jira Issue tracker for CUBRID
  6. [6]
    Stevens, O. (Oct–Dec 2009). "The History of Datacom/DB". Annals of the History of Computing. 31 (4). IEEE: 87–91. doi:10.1109/MAHC.2009.108. ISSN 1058-6180. S2CID 16803811.
  7. [7]
    "CA Datacom - CA Technologies". Archived from the original on 2016-02-14. Retrieved 2014-07-06.
  8. [8]
    "Datacom Product Sheet" (PDF).
  9. [9]
    "Db2 Documentation". Retrieved 15 November 2023.
  10. [10]
    "Firebird 5.0.0". 11 January 2024. Retrieved 14 January 2024.
  11. [11]
    IPL, Firebird SQL
  12. [12]
    IDPL, Firebird SQL
  13. [13]
    Firebird RDBMS Issue Tracker
  14. [14]
    HyperSQL Database Engine (HSQLDB) / Bugs
  15. [15]
    h2database issues
  16. [16]
    "Actian X & Ingres - Lifecycle Dates".
  17. [17]
    Linter Techsupport
  18. [18]
    "MariaDB 11.3.2 Release Notes".
  19. [19]
    "MariaDB licenses".
  20. [20]
    MariaDB - JIRA
  21. [21]
    MaxDB - Problem Tracking
  22. [22]
    "Explore SQL Server 2022 capabilities". Retrieved 6 January 2023.
  23. [23]
    "MonetDB Solutions".
  24. [24]
    "MonetDB Latest Release".
  25. [25]
    MonetDB License MPL2.0, MonetDB B.V., 8 February 2022
  26. [26]
    MonetDB Issues
  27. [27]
    mSQL, Products, AU: Hughes, archived from the original on 2009-10-15, retrieved 2009-09-13
  28. [28]
    "Changes in MySQL 8.3.0 (2024-01-16, Innovation Release)". 16 January 2024. Retrieved 16 January 2024.
  29. [29]
    MySQL Bugs
  30. [30]
    Issues · openlink/virtuoso-opensource · GitHub
  31. [31]
    "Oracle Database 23c: The Next Long Term Support Release".
  32. [32]
    "Oracle Rdb Product Family Compatibility Matrix". oracle.com.
  33. [33]
    Polyhedra Lite In-Memory Relational Database System Freeware Available Now from Enea, Press Release, EECatalog.
  34. [34]
    "PostgreSQL 16.1, 15.5, 14.10, 13.13, 12.17, and 11.22 Released!". PostgreSQL. The PostgreSQL Global Development Group. 2023-11-09. Retrieved 2023-11-29.
  35. [35]
    Postgres License
  36. [36]
    A bug tracker for PostgreSQL?
  37. [37]
    "SQLite Release 3.45.3 On 2024-04-15". 15 April 2024. Retrieved 15 April 2024.
  38. [38]
    SQLite: Ticket Main Menu
  39. [39]
    SQream DB Version 2.1 SQL Reference Guide, SQream Technologies
  40. [40]
    "Bug Reports".
  41. [41]
    "Release 7.6.0". 25 January 2024. Retrieved 20 February 2024.
  42. [42]
    "Issues · pingcap/Tidb". GitHub.
  43. [43]
    "yugabyte/yugabyte-db". github.com.
  44. [44]
    "Issues · yugabyte/Yugabyte-db". GitHub.
  45. [45]
    "Firebird: The true open source database for Windows, Linux, Mac OS X and more".
  46. [46]
    "Ingres 11".
  47. [47]
    "Building MariaDB on Mac OS X using Homebrew". AskMonty KnowledgeBase. Archived from the original on October 20, 2011. Retrieved September 30, 2011.
  48. [48]
    https://play.google.com/store/apps/details?id=com.esminis.server.mariadb&hl=de MariaDB Android Version by Tautvydas Andrikys
  49. [49]
    "Announcing SQL Server on Linux". 7 March 2016.
  50. [50]
    "Mimer SQL is now available for OpenVMS on x86".
  51. [51]
    http://techotv.com/run-apache-mysql-php-http-web-server-android-os-phone-tablet/ Run Apache, Mysql, Php – Web server on Android mobile or Tablet
  52. [52]
    "Aminet - dev/Gg/Postgresql632-mos-bin.lha".
  53. [53]
    "PostgreSQL - Oss4zos". Archived from the original on 2015-05-27. Retrieved 2013-08-15.
  54. [54]
    Derby Developer's Guide (10.14)>Lock granularity
  55. [55]
    DB2 for Linux UNIX and Windows 9.7.0>Fundamentos de DB2>Performance tuning>Factors affecting performance>Application design>Concurrency issues>Isolation levels
  56. [56]
    "Advanced".
  57. [57]
    Transactional DDL in PostgreSQL: A Competitive Analysis
  58. [58]
    Transactional DDL in MariaDB
  59. [59]
    SQL Server Transaction Locking and Row Versioning Guide
  60. [60]
    MySQL :: MySQL 5.6 Reference Manual :: 8.10.1 Internal Locking Methods
  61. [61]
    Oracle Row Lock and Row Level Locking
  62. [62]
    "Polyhedra 8.7 new headline feature: locking".
  63. [63]
    PostgreSQL: Documentation: Explicit Locking : Row-Level Locks
  64. [64]
    BUG #5974: UNION construct type cast gives poor error message
  65. [65]
    https://help.sap.com/viewer/e38b2f6217f24bdb90a3ff8ae57b1dd5/17.0/en-US/3bee03b56c5f1014ab68e3eff32515dd.doc | SAP SQL Anywhere Reference - Types of Lock
  66. [66]
    SAP SQL Anywhere Reference - Snapshot Isolation
  67. [67]
    https://help.sap.com/viewer/98ad9ec940e2465695685d98e308dff5/17.0/en-US/3bd460b56c5f10148922c11d39abc0b3.doc | SAP SQL Anywhere Reference - HTTP Web Services
  68. [68]
    File Locking And Concurrency In SQLite Version 3
  69. [69]
    SQLite Full Unicode support is optional and not installed by default in most systems (like Android, Debian...)
  70. [70]
    TiDB Features
  71. [71]
    "MySQL - The InnoDB Storage Engine".
  72. [72]
    "InnoDB - Oracle Wiki".
  73. [73]
    "MySQL 5.6 Reference Manual".
  74. [74]
    "Identifier Names". MariaDB KnowledgeBase. Retrieved 26 September 2014.
  75. [75]
    "PostgreSQL Limits". Retrieved 2021-05-13.
  76. [76]
    "Large Objects: Introduction". Retrieved 2021-05-13.
  77. [77]
    "Date/Time Types". Retrieved 2021-05-13.
  78. [78]
    https://help.sap.com/viewer/61ecb3d4d8be4baaa07cc4db0ddb5d0a/17.0/en-US/813836f16ce210149e89f219dc353b7e.doc | SAP SQL Anywhere - Physical limitations on size and number of databases
  79. [79]
    Technical Specifications, Guide, Firebird SQL, archived from the original on 2010-06-15, retrieved 2008-03-30
  80. [80]
    Library, MSDN, Microsoft
  81. [81]
    "Column count limit", Reference Manual, MySQL 5.1 Documentation, Oracle
  82. [82]
    "Row-Overflow Considerations", TechNet Library, SQL Server Documentation, Microsoft, 2012
  83. [83]
    "Date functions", Language, SQLite
  84. [84]
    Online books, Sybase, archived from the original on 2005-10-23
  85. [85]
    Informix Performance Guide, Info Centre, IBM
  86. [86]
    Dynamic Materialized Views in MySQL, Pure, Red Noize, 2005, archived from the original on 2006-04-23
  87. [87]
    "Derby", Full Text Indexing, Search, Issues, Apache
  88. [88]
    "CUBRID 9.0 release". Archived from the original on 2013-02-14. Retrieved 2013-02-05.
  89. [89]
    Full-text search with Db2 Text Search, Developer Works, IBM
  90. [90]
    Does Firebird support full-text search?, Firebird FAQ
  91. [91]
    Fulltext Search, Tutorial, H2 Database
  92. [92]
    Create Spatial Index, Grammar, H2 Database
  93. [93]
    Forest of Trees Index, Informix Infocenter, IBM, 20 July 2022
  94. [94]
    Full Text Search Functions (PDF), Documentation, RU: Linter, archived from the original (PDF) on 2011-08-20, retrieved 2010-06-06
  95. [95]
    SPATIAL INDEX, MariaDB, mariadb.com, retrieved 24 September 2017
  96. [96]
    "Storage Engine Index Types". mariadb.com. Retrieved 25 April 2016.
  97. [97]
    Virtual Columns - MariaDB Knowledge Base
  98. [98]
    "Fulltext Index Overview". mariadb.com. Retrieved 25 April 2016.
  99. [99]
    Does Microsoft Access have Full Text Search?, Questions, Stack Overflow
  100. [100]
    "Microsoft SQL Server Full-Text Search", Library, MSDN, Microsoft
  101. [101]
    "Spatial Indexing Overview", Library, Tech Net, Microsoft
  102. [102]
    "Microsoft SQL Server Compact Full-text search is not available", Forums, MSDN, Microsoft
  103. [103]
    Index Types Per Storage Engine, MySQL, Oracle, retrieved 24 September 2017
  104. [104]
    "Feature request #4990: Functional Indexes", Bugs, MySQL, Oracle
  105. [105]
    "Feature request #13979: InnoDB engine doesn't support FULLTEXT", Bugs, MySQL, Oracle
  106. [106]
    "MySQL v5.6.4 Release Notes", Release Notes, MySQL, Oracle
  107. [107]
    Creating Spatial Indexes, MySQL, Oracle
  108. [108]
    Changes in MySQL 5.7.5, MySQL, Oracle
  109. [109]
    Does Oracle support full text search?, Questions, Stack Overflow
  110. [110]
    "Location Features for Database 11g", Spatial & Locator, Tech Network, Oracle
  111. [111]
    Oracle / PLSQL: ORA-01408 Error Message
  112. [112]
    Index Types, Documentation, PostgreSQL community, 11 November 2021
  113. [113]
    Full Text Search, Documentation, PostgreSQL community, 11 November 2021
  114. [114]
    Building Spatial Indexes, PostGIS Manual, The PostGIS Development Group
  115. [115]
    The SQLite R*Tree Module
  116. [116]
    SQLite Expression Indexes
  117. [117]
    SQLite FTS5 Extension
  118. [118]
    SpatiaLite, IT: Gaia GIS 2.3.1, archived from the original on 2011-07-22, retrieved 2010-12-06
  119. [119]
    Full-Text Search, Online Publications, Teradata
  120. [120]
    geospatial
  121. [121]
    UDF, Ad Hoc Data, archived from the original on 2019-09-14, retrieved 2007-01-11
  122. [122]
    "Create DB", Library, MSDN, Microsoft
  123. [123]
    "SQL", Library, MSDN, Microsoft
  124. [124]
    Petkovic, Dusan (2005). Microsoft SQL Server 2005: A Beginner's Guide. McGraw-Hill Professional. p. 300. ISBN 978-0-07-226093-9.
  125. [125]
    "InnoDB adaptive Hash", Reference manual 5.0, Development documentation, Oracle
  126. [126]
    "Article", Library, Developer Works, IBM
  127. [127]
    "What's new in MariaDB 10.3".
  128. [128]
    New Features in HyperSQL 2.2
  129. [129]
    H2 > Advanced > Recursive Queries
  130. [130]
    H2 Functions
  131. [131]
    Informix parallel data query (PDQ)
  132. [132]
    "Ingres".
  133. [133]
    "Ingres".
  134. [134]
    "Ingres".
  135. [135]
    "INTERSECT". mariadb.com.
  136. [136]
    "EXCEPT". mariadb.com.
  137. [137]
    "CTE implemented in 10.2.2". mariadb.org. Retrieved 26 July 2017.
  138. [138]
    "Window Functions Overview". mariadb.com. Retrieved 25 April 2016.
  139. [139]
    "Feature request #1542: Parallel query", Bugs, MySQL, Oracle
  140. [140]
    Only very limited functions available before SQL Server 2012, Microsoft
  141. [141]
    "SQL Server Parallel Query Processing", Library, MSDN, Microsoft
  142. [142]
    "Feature request #16244: SQL-99 Derived table WITH clause (CTE)", Bugs, MySQL, Oracle
  143. [143]
    Window Functions, mysql.com, retrieved 20 July 2021
  144. [144]
    Parallel Query, Wiki, Ora FAQ
  145. [145]
    "New Features Oracle 12.1.0.1". Archived from the original on 2020-10-25.
  146. [146]
    Parallel Query, PostgreSQL, 11 August 2022
  147. [147]
    SQLite Query Language: WITH clause
  148. [148]
    Window Functions
  149. [149]
    "Data Types", General Reference, HDB, Altibase
  150. [150]
    "10. Data Types", Reference manual, MySQL 5.0, Oracle
  151. [151]
    "Data Types", CUBRID SQL Guide, Reference Manual, CUBRID[permanent dead link]
  152. [152]
    "FileMaker 14 Tech Specs". FileMaker=May 12, 2015.
  153. [153]
    "Migration from MS-SQL to Firebird". Firebird Project. Retrieved April 12, 2015.
  154. [154]
    "General: HSQLDB data types", Guide, 2.0 Documents, HSQLDB
  155. [155]
    "IBM Informix Guide to SQL: Reference, v11.50 (SC23-7750-04)". Publications. IBM. Retrieved August 7, 2013.
  156. [156]
    "3: Understanding SQL Data Types", SQL 9.3 Reference Guide, Documents, Ingres
  157. [157]
    "Data Types". mariadb.com. Retrieved 25 April 2016.
  158. [158]
    "SQL Server Data Types", Library, MSDN, Microsoft
  159. [159]
    "SQL Server Compact Data Types", Library, MSDN, Microsoft
  160. [160]
    "Datatypes", SQL Reference, OpenLink Software
  161. [161]
    "Data Types", SQL 11.2 Reference, Server documents, Oracle, archived from the original on 2010-03-14, retrieved 2009-09-21
  162. [162]
    "Data Types", Pervasive PSQL Supported Data Types, Product documentation, Pervasive
  163. [163]
    Polyhedra SQL Reference Manual, Product documentation, Enea AB, archived from the original on 2013-10-04, retrieved 2013-04-23
  164. [164]
    "Data Types", Manual, PostgreSQL 10 Documentation, PostgreSQL community, 11 August 2022
  165. [165]
    Datatypes, SQLite 3
  166. [166]
    SQream SQL Reference Guide, SQream Technologies
  167. [167]
    "CONSTRAINT". mariadb.com.
  168. [168]
    Support, Downloads, Sybase, retrieved 2008-09-07[dead link]
  169. [169]
    "Release", Engine, Development, Firebird SQL 2.0
  170. [170]
    Files, Firebird SQL
  171. [171]
    "Trace and Audit Services". Firebird Project. Retrieved April 12, 2015.
  172. [172]
    "cracklib_password_check". mariadb.com. Retrieved 9 December 2014.
  173. [173]
    "simple_password_check". mariadb.com. Retrieved 9 December 2014.
  174. [174]
    "Security Vulnerabilities Fixed in MariaDB". mariadb.com. Retrieved 25 April 2016.
  175. [175]
    "Downloads", Development, MySQL, Oracle
  176. [176]
    Security, Support, PostgreSQL community, archived from the original on 2011-11-01, retrieved 2018-03-05
  177. [177]
    Open Source PostgreSQL Audit Logging, September 2022
  178. [178]
    Download, SQLite
  179. [179]
    DB, Products, Common Criteria Portal, retrieved 2021-05-13
  180. [180]
    Backup MySQL, How to, Gentoo wiki, archived from the original on 2008-09-02, retrieved 2008-09-07
  181. [181]
    Authentication methods, 8.1 Documents, PostgreSQL community, 24 July 2014
  182. [182]
    Common Criteria (CC, ISO15408), Microsoft, archived from the original on 2014-02-13
  183. [183]
    Adding audit trails to a Polyhedra IMDB database, White paper, Enea AB
  184. [184]
    "PostgreSQL: Documentation: IMPORT FOREIGN SCHEMA". www.postgresql.org. Retrieved 2016-06-11.
Wikibooks has a book on the topic of: SQL dialects reference
Share this article:

This article uses material from the Wikipedia article Comparison_of_relational_database_management_systems, and is written by contributors. Text is available under a CC BY-SA 4.0 International License; additional terms may apply. Images, videos and audio are available under their respective licenses.