Comparison of relational database management systems
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
Operating system support
The operating systems that the RDBMSes can run on.Windows | macOS | Linux | BSD | UNIX | AmigaOS | z/OS | iOS | Android | OpenVMS | |
4th Dimension | ||||||||||
ADABAS | ||||||||||
Adaptive Server Enterprise | ||||||||||
Advantage Database Server | ||||||||||
Altibase | ||||||||||
Apache Derby | ||||||||||
ClustrixDB | ||||||||||
CUBRID | ||||||||||
DB2 | ||||||||||
Empress Embedded Database | ||||||||||
EXASolution | ||||||||||
FileMaker | ||||||||||
Firebird | ||||||||||
HSQLDB | ||||||||||
H2 | ||||||||||
Informix Dynamic Server | ||||||||||
Ingres | ||||||||||
InterBase | ||||||||||
Linter SQL RDBMS | Under Linux on IBM Z | |||||||||
LucidDB | ||||||||||
MariaDB | ||||||||||
MaxDB | ||||||||||
Microsoft Access | ||||||||||
Microsoft Visual Foxpro | ||||||||||
Microsoft SQL Server | ||||||||||
Microsoft SQL Server Compact | ||||||||||
Mimer SQL | ||||||||||
MonetDB | ||||||||||
MySQL | ||||||||||
Omnis Studio | ||||||||||
OpenEdge | ||||||||||
OpenLink Virtuoso | ||||||||||
Oracle | ||||||||||
Oracle Rdb | ||||||||||
Pervasive PSQL | ||||||||||
Polyhedra | ||||||||||
PostgreSQL | Under Linux on IBM Z | |||||||||
Raima Database Manager | ||||||||||
RDM Server | ||||||||||
SAP HANA | ||||||||||
solidDB | Under Linux on IBM Z | |||||||||
SQL Anywhere | ||||||||||
SQLBase | ||||||||||
SQLite | ||||||||||
SQream DB | ||||||||||
Superbase | ||||||||||
Teradata | ||||||||||
Tibero | ||||||||||
UniData | ||||||||||
UniVerse | ||||||||||
YugabyteDB | ||||||||||
Windows | macOS | Linux | BSD | UNIX | AmigaOS | z/OS | iOS | Android | OpenVMS |
Fundamental features
Information about what fundamental RDBMS features are implemented natively.Database Name | ACID | Referential integrity | Transactions | Fine-grained locking | Multiversion concurrency control | Unicode | Interface | Type inference |
4th Dimension | GUI & SQL | |||||||
ADABAS | proprietary direct call & SQL | |||||||
Adaptive Server Enterprise | Yes | API & GUI & SQL | ||||||
Advantage Database Server | [|4] | API & SQL | ||||||
Altibase | API & GUI & SQL | |||||||
Apache Derby | SQL | |||||||
ClustrixDB | SQL | |||||||
CUBRID | GUI & SQL | |||||||
DB2 | GUI & SQL | |||||||
Empress Embedded Database | API & SQL | |||||||
EXASolution | API & GUI & SQL | |||||||
Firebird | API & SQL | |||||||
HSQLDB | SQL | |||||||
H2 | SQL | |||||||
Informix Dynamic Server | SQL, REST, and JSON | |||||||
Ingres | SQL & QUEL | |||||||
InterBase | SQL | |||||||
Linter SQL RDBMS | API & GUI & SQL | |||||||
LucidDB | SQL | |||||||
MariaDB | [|2] | [|6] | 2 except for DDL | SQL | ||||
MaxDB | SQL | |||||||
Microsoft Access | GUI & SQL | |||||||
Microsoft Visual FoxPro | GUI & SQL | |||||||
Microsoft SQL Server | GUI & SQL | |||||||
Microsoft SQL Server Compact | GUI & SQL | |||||||
Mimer SQL | API & GUI & SQL | |||||||
MonetDB | API & SQL & MAL | |||||||
MySQL | 2 | 3 | 2 except for DDL | GUI [|5] & SQL | ||||
OpenEdge | 7 | GUI & SQL | ||||||
OpenLink Virtuoso | API & GUI & SQL | |||||||
Oracle | except for DDL | API & GUI & SQL | ||||||
Oracle Rdb | SQL | |||||||
Pervasive PSQL | 6 | API & GUI & SQL | ||||||
Polyhedra DBMS | API & SQL | |||||||
PostgreSQL | API & GUI & SQL | |||||||
Raima Database Manager | SQL & API | |||||||
RDM Server | SQL & API | |||||||
SAP HANA | API & GUI & SQL | |||||||
solidDB | API & SQL | |||||||
SQL Anywhere | API & GUI & HTTP & SQL | |||||||
SQLBase | API & GUI & SQL | |||||||
SQLite | API & SQL | |||||||
Teradata | SQL | |||||||
Tibero | API & GUI & SQL | |||||||
UniData | Multiple | |||||||
UniVerse | Multiple | |||||||
Database Name | ACID | Referential integrity | Transactions | Fine-grained locking | Multiversion concurrency control | Unicode | Interface | Type inference |
Note : Currently only supports read uncommited transaction isolation. Version [|1].[|9] adds serializable isolation and version 2.0 will be fully ACID compliant.
Note : MySQL provides ACID compliance through the default InnoDB storage engine.
Note : "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."
Note : Support for Unicode is new in version [|10].0.
Note : MySQL provides GUI interface through MySQL Workbench.
Note : MariaDB's default XtraDB engine is ACID compliant.
Note : 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.Max DB size | Max table size | Max row size | Max columns per row | Max Blob/Clob size | Max CHAR size | Max NUMBER size | Min DATE value | Max DATE value | Max column name size | |
4th Dimension | Limited | 65,135 | 200 GB | 200 GB | 64 bits | |||||
Advantage Database Server | Unlimited | 16 EiB | 65,530 B | 65,135 / | 4 GiB | 64 bits | 128 | |||
Apache Derby | Unlimited | Unlimited | Unlimited | 1,012 | 2,147,483,647 chars | 254 | 64 bits | 0001-01-01 | 9999-12-31 | 128 |
ClustrixDB | Unlimited | Unlimited | 64 MB on Appliance, 4 MB on AWS | 64 MB | 64 MB | 64 MB | 0001-01-01 | 9999-12-31 | 254 | |
CUBRID | 2 EB | 2 EB | Unlimited | Unlimited | Unlimited | 1 GB | 64 bits | 0001-01-01 | 9999-12-31 | 254 |
DB2 | Unlimited | 2 ZB | 1,048,319 B | 1,012 | 2 GB | 32 KiB | 64 bits | 0001-01-01 | 9999-12-31 | 128 |
Empress Embedded Database | Unlimited | 263-1 bytes | 2 GB | 32,767 | 2 GB | 2 GB | 64 bits | 0000-01-01 | 9999-12-31 | 32 |
EXASolution | Unlimited | Unlimited | Unlimited | 10,000 | N/A | 2 MB | 128 bits | 0001-01-01 | 9999-12-31 | 256 |
FileMaker | [|8] TB | 8 TB | 8 TB | 256,000,000 | 4 GB | 10,000,000 | 1 billion characters, 10^-400 to 10^400, +- | 0001-01-01 | 4000-12-31 | 100 |
Firebird | Unlimited1 | ~32 TB | 65,536 B | Depends on data types used | 32 GB | 32,767 B | 64 bits | 100 | 32768 | 31 |
HSQLDB | 64 TB | Unlimited8 | Unlimited8 | Unlimited8 | 64 TB7 | Unlimited8 | Unlimited8 | 0001-01-01 | 9999-12-31 | 128 |
H2 | 64 TB | Unlimited8 | Unlimited8 | Unlimited8 | 64 TB7 | Unlimited8 | 64 bits | -99999999 | 99999999 | Unlimited8 |
Max DB size | Max table size | Max row size | Max columns per row | Max Blob/Clob size | Max CHAR size | Max NUMBER size | Min DATE value | Max DATE value | Max column name size | |
Informix Dynamic Server | ~128 PB12 | ~128 PB12 | 32,765 bytes | 32,765 | 4 TB | 32,765 | 1032 | 01/01/000110 | 12/31/9999 | 128 bytes |
Ingres | Unlimited | Unlimited | 256 KB | 1,024 | 2 GB | 32 000 B | 64 bits | 0001 | 9999 | 256 |
InterBase | Unlimited1 | ~32 TB | 65,536 B | Depends on data types used | 2 GB | 32,767 B | 64 bits | 100 | 32768 | 31 |
Linter SQL RDBMS | Unlimited | 230 rows | 64 KB, 2GB | 250 | 2 GB | 4000 B | 64 bits | 0001-01-01 | 9999-12-31 | 66 |
MariaDB | Unlimited | MyISAM storage limits: 256 TB; Innodb storage limits: 64 TB; Aria storage limits: ??? | 64 KB3 | 4,0964 | 4 GB | 64 KB | 64 bits | 1000 | 9999 | 64 |
Microsoft Access | 2 GB | 2 GB | 16 MB | 255 | 64 KB, 1 GB | 255 B | 32 bits | 0100 | 9999 | 64 |
Microsoft Visual Foxpro | Unlimited | 2 GB | 65,500 B | 255 | 2 GB | 16 MB | 32 bits | 0001 | 9999 | 10 |
Microsoft SQL Server | 524,272 TB 16ZB per instance | 524,272 TB | 8,060 bytes/2TB6 | 1,024/30,000 | 2 GB/Unlimited | 2 GB6 | 126 bits2 | 0001 | 9999 | 128 |
Microsoft SQL Server Compact | 4 GB | 4 GB | 8,060 bytes | 1024 | 2 GB | 4000 | 154 bits | 0001 | 9999 | 128 |
Mimer SQL | Unlimited | Unlimited | 16000 | 252 | Unlimited | 15000 | 45 digits | 0001-01-01 | 9999-12-31 | 128 |
MonetDB | Unlimited | Unlimited | Unlimited | Unlimited | 2 GB | 2 GB | 128 bits | -9999-01-01 | 9999-12-31 | 1024 |
MySQL | Unlimited | MyISAM storage limits: 256 TB; Innodb storage limits: 64 TB | 64 KB3 | 4,0964 | 4 GB | 64 KB | 64 bits | 1000 | 9999 | 64 |
OpenLink Virtuoso | 32 TB per instance | DB size | 4 KB | 200 | 2 GB | 2 GB | 231 | 0 | 9999 | 100 |
Oracle | 2PB 8PB 8EB | 4 GB * block size | 8 KB | 1,000 | 128 TB | 32,767 B11 | 126 bits | −4712 | 9999 | 128 |
Max DB size | Max table size | Max row size | Max columns per row | Max Blob/Clob size | Max CHAR size | Max NUMBER size | Min DATE value | Max DATE value | Max column name size | |
Pervasive PSQL | 4 billion objects | 256 GB | 2 GB | 1,536 | 2 GB | 8,000 bytes | 64 bits | 01-01-0001 | 12-31-9999 | 128 bytes |
Polyhedra | Limited by available RAM, address space | 232 rows | Unlimited | 65,536 | 4 GB | 4 GB | 64 bits | 0001-01-01 | 8000-12-31 | 255 |
PostgreSQL | Unlimited | 32 TB | 1.6 TB | 250–1600 depending on type | 1 GB stored inline or 4 TB | 1 GB | Unlimited | −4,713 | 5,874,897 | 63 |
Raima Database Manager | Unlimited | 248-1 rows | 32 KB | 1,000 | 4 GB | char: 256, varchar: 4 KB | 64 bits | 0001-01-01 | 11758978-12-31 | 31 |
RDM Server | Unlimited | 264-1 rows | 32 KB | 32,768 | Unlimited | 32 KB | 64 bits | 0001-01-01 | 11758978-12-31 | 32 |
SAP HANA | ||||||||||
solidDB | 256 TB | 256 TB | 32 KB + BLOB data | Limited by row size | 4 GB | 4 GB | 64 bits | -32768-01-01 | 32767-12-31 | 254 |
SQL Anywhere | 104 TB | Limited by file size | Limited by file size | 45,000 | 2 GB | 2 GB | 64 bits | 0001-01-01 | 9999-12-31 | 128 bytes |
SQLite | 128 TB | Limited by file size | Limited by file size | 32,767 | 2 GB | 2 GB | 64 bits | No DATE type9 | No DATE type9 | Unlimited |
Teradata | Unlimited | Unlimited | 64000 wo/lobs | 2,048 | 2 GB | 64,000 | 38 digits | 0001-01-01 | 9999-12-31 | 128 |
UniVerse | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited |
Max DB size | Max table size | Max row size | Max columns per row | Max Blob/Clob size | Max CHAR size | Max NUMBER size | Min DATE value | Max DATE value | Max column name size |
Note : Firebird 2.x maximum database size is effectively unlimited with the largest known database size >980 GB. Firebird 1.5.x maximum database size: 32 TB.
Note : Limit is 1038 using
DECIMAL
datatype.Note : InnoDB is limited to 8,000 bytes.
Note : InnoDB is limited to 1,017 columns.
Note : Using
VARCHAR
in SQL 2005 and later.Note : When using a page size of 32 KB, and when BLOB/CLOB data is stored in the database file.
Note : Java array size limit of 2,147,483,648 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 : Despite the lack of a date datatype, SQLite does include date and time functions, which work for timestamps between 24 November 4714 B.C. and 1 November 5352.
Note : 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 : Since version 12c. Earlier versions support up to 4000 B.
Note : The 128PB 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.
Tables and views
Information about what tables and views are supported natively.Temporary table | Materialized view | |
4th Dimension | ||
ADABAS | ||
Adaptive Server Enterprise | 1 | - see precomputed result sets |
Advantage Database Server | ||
Altibase | ||
Apache Derby | ||
ClustrixDB | ||
CUBRID | ||
DB2 | ||
Empress Embedded Database | ||
EXASolution | ||
Firebird | ||
HSQLDB | ||
H2 | ||
Informix Dynamic Server | 2 | |
Ingres | ||
InterBase | ||
Linter SQL RDBMS | ||
LucidDB | ||
MariaDB | 4 | |
MaxDB | ||
Microsoft Access | ||
Microsoft Visual Foxpro | ||
Microsoft SQL Server | ||
Microsoft SQL Server Compact | ||
Mimer SQL | ||
MonetDB | ||
MySQL | 4 | |
Oracle | ||
Oracle Rdb | ||
OpenLink Virtuoso | ||
Pervasive PSQL | ||
Polyhedra DBMS | ||
PostgreSQL | 5 | |
Raima Database Manager | ||
RDM Server | ||
SAP HANA | ||
solidDB | ||
SQL Anywhere | ||
SQLite | ||
Teradata | ||
UniData | ||
UniVerse | ||
Temporary table | Materialized view |
Note : Server provides tempdb, which can be used for public and private temp tables.
Note : 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.
Note : Materialized views can be emulated using stored procedures and triggers.
Note : Materialized views are now standard.
Indexes
Information about what indexes are supported natively.R-/R+ tree | Hash | Expression | Partial | Reverse | Bitmap | GiST | GIN | Full-text | Spatial | FOT | Duplicate index prevention | |
4th Dimension | Cluster | |||||||||||
ADABAS | ||||||||||||
Adaptive Server Enterprise | ||||||||||||
Advantage Database Server | ||||||||||||
Apache Derby | ||||||||||||
ClustrixDB | ||||||||||||
CUBRID | ||||||||||||
DB2 | ||||||||||||
Empress Embedded Database | ||||||||||||
EXASolution | ||||||||||||
Firebird | ||||||||||||
HSQLDB | ||||||||||||
H2 | ||||||||||||
Informix Dynamic Server | ||||||||||||
Ingres | ||||||||||||
InterBase | ||||||||||||
Linter SQL RDBMS10 | temporary indexes for equality joins | for some scalar functions like LOWER and UPPER | ||||||||||
LucidDB | ||||||||||||
MariaDB | Aria and MyISAM tables and, since v10.2.2, InnoDB tables only | MEMORY, InnoDB,5 tables only | PERSISTENT virtual columns only | Aria and MyISAM tables and, since v10.2.2, InnoDB tables only | ||||||||
MaxDB | ||||||||||||
Microsoft Access | ||||||||||||
Microsoft Visual Foxpro | 2 | |||||||||||
Microsoft SQL Server | Spatial Indexes | 4 | 3 | on Computed columns3 | Bitmap filter index for Star Join Query | |||||||
Microsoft SQL Server Compact | ||||||||||||
Mimer SQL | ||||||||||||
MonetDB | ||||||||||||
MySQL | Spatial Indexes | MEMORY, Cluster, InnoDB,5 tables only | MyISAM tables and, since v5.6.4, InnoDB tables | MyISAM tables and, since v5.7.5, InnoDB tables | ||||||||
OpenLink Virtuoso | Cluster | |||||||||||
Oracle | 11 | Cluster Tables | 6 | |||||||||
Oracle Rdb | ||||||||||||
Pervasive PSQL | ||||||||||||
Polyhedra DBMS | ||||||||||||
PostgreSQL | 7 | PostGIS | ||||||||||
Raima Database Manager | ||||||||||||
RDM Server | ||||||||||||
SAP HANA | ||||||||||||
solidDB | ||||||||||||
SQL Anywhere | ||||||||||||
SQLite | SpatiaLite | |||||||||||
SQream DB | ||||||||||||
Teradata | ||||||||||||
UniVerse | 3 | 3 | 3 | |||||||||
R-/R+ tree | Hash | Expression | Partial | Reverse | Bitmap | GiST | GIN | Full-text | Spatial | FOT | Duplicate index prevention |
Note : The users need to use a function from freeAdhocUDF library or similar.
Note : Can be implemented for most data types using expression-based indexes.
Note : Can be emulated by indexing a computed column or by using an "Indexed View".
Note : Used for InMemory ColumnStore index, temporary hash index for hash join, Non/Cluster & fill factor.
Note : InnoDB automatically generates adaptive hash index entries as needed.
Note : 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 : A PostgreSQL functional index can be used to reverse the order of a field.
Note : B+ tree and full-text only for now.
Note : R-Tree indexing available in base edition with Locator but some functionality requires Personal Edition or Enterprise Edition with Spatial option.
Database capabilities
Note :Recursive CTEs introduced in 11gR2 supersedes similar construct called CONNECT BY.
Data types
Other objects
Information about what other objects are supported natively.Data Domain | Cursor | Trigger | Function 1 | Procedure 1 | External routine 1 | |
4th Dimension | ||||||
ADABAS | ? | ? | ||||
Adaptive Server Enterprise | ||||||
Advantage Database Server | ||||||
Altibase | ||||||
Apache Derby | 2 | 2 | 2 | |||
ClustrixDB | ||||||
CUBRID | 2 | |||||
Empress Embedded Database | via RANGE CHECK | |||||
EXASolution | ||||||
DB2 | via CHECK CONSTRAINT | |||||
Firebird | ||||||
HSQLDB | ||||||
H2 | 2 | 2 | 2 | |||
Informix Dynamic Server | via CHECK | 5 | ||||
Ingres | ||||||
InterBase | ||||||
Linter SQL RDBMS | ||||||
LucidDB | 2 | 2 | 2 | |||
MariaDB | ||||||
MaxDB | ||||||
Microsoft Access | ||||||
Microsoft Visual Foxpro | ||||||
Microsoft SQL Server | ||||||
Microsoft SQL Server Compact | ||||||
Mimer SQL | ||||||
MonetDB | ||||||
MySQL | 3 | |||||
OpenBase SQL | ||||||
Oracle | ||||||
Oracle Rdb | ||||||
OpenLink Virtuoso | ||||||
Pervasive PSQL | ||||||
Polyhedra DBMS | ||||||
PostgreSQL | ||||||
Raima Database Manager | ||||||
RDM Server | ||||||
SAP HANA | ||||||
solidDB | ||||||
SQL Anywhere | ||||||
SQLite | ||||||
Teradata | ||||||
UniData | ||||||
UniVerse | ||||||
Data Domain | Cursor | Trigger | Function 1 | Procedure 1 | External routine 1 |
Note : 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 : In Derby, H2, LucidDB, and CUBRID, users code functions and procedures in Java.
Note : ENUM datatype exists. CHECK clause is parsed, but not enforced in runtime.
Note : Informix supports external functions written in Java, C, & C++.
Partitioning
Information about what partitioning methods are supported natively.Range | Hash | Composite | List | Expression | Round Robin | |
4th Dimension | ||||||
ADABAS | ||||||
Adaptive Server Enterprise | ||||||
Advantage Database Server | ||||||
Altibase | ||||||
Apache Derby | ||||||
ClustrixDB | ||||||
CUBRID | ||||||
IBM DB2 | ||||||
Empress Embedded Database | ||||||
EXASolution | ||||||
Firebird | ||||||
HSQLDB | ||||||
H2 | ||||||
Informix Dynamic Server | ||||||
Ingres | ||||||
InterBase | ||||||
Linter SQL RDBMS | ||||||
MariaDB | ||||||
MaxDB | ||||||
Microsoft Access | ||||||
Microsoft Visual Foxpro | ||||||
Microsoft SQL Server | ||||||
Microsoft SQL Server Compact | ||||||
Mimer SQL | ||||||
MonetDB | ||||||
MySQL | ||||||
OpenBase SQL | ||||||
Oracle | ||||||
Oracle Rdb | ||||||
OpenLink Virtuoso | ||||||
Pervasive PSQL | ||||||
Polyhedra DBMS | ||||||
PostgreSQL | ||||||
Raima Database Manager | 1 | 1 | 1 | |||
RDM Server | ||||||
SAP HANA | ||||||
solidDB | ||||||
SQL Anywhere | ||||||
SQLite | ||||||
Teradata | ||||||
UniVerse | ||||||
Range | Hash | Composite | List | Expression | Round Robin |
Note : Raima Database Manager 14.0 requires the application programs to select the correct partition when adding data, but the database union functionality allows all partitions to be read as a single database.
Access control
Information about access control functionalities.Native network encryption1 | Brute-force protection | Enterprise directory compatibility | Password complexity rules2 | Patch access3 | Run unprivileged4 | Audit | Resource limit | Separation of duties 5 | Security Certification | Attribute-Based Access Control | |
4D | |||||||||||
Adaptive Server Enterprise | |||||||||||
Advantage Database Server | |||||||||||
DB2 | |||||||||||
Empress Embedded Database | |||||||||||
EXASolution | |||||||||||
Firebird | 7 | ||||||||||
HSQLDB | |||||||||||
H2 | |||||||||||
Informix Dynamic Server | 10 | 10 | |||||||||
Linter SQL RDBMS | |||||||||||
MariaDB | 8 | ||||||||||
Microsoft SQL Server | |||||||||||
Microsoft SQL Server Compact | |||||||||||
Mimer SQL | |||||||||||
MySQL | 8 | ||||||||||
OpenBase SQL | |||||||||||
OpenLink Virtuoso | |||||||||||
Oracle | |||||||||||
Pervasive PSQL | 12 | ||||||||||
Polyhedra DBMS | 13 | 13 | |||||||||
PostgreSQL | , with triggers | ||||||||||
Raima Database Manager | |||||||||||
RDM Server | |||||||||||
SAP HANA | |||||||||||
solidDB | |||||||||||
SQL Anywhere | |||||||||||
SQLite | |||||||||||
Teradata | |||||||||||
Native network encryption1 | Brute-force protection | Enterprise directory compatibility | Password complexity rules2 | Patch access3 | Run unprivileged4 | Audit | Resource limit | Separation of duties 5 | Security Certification | Attribute-Based Access Control |
Note : Network traffic could be transmitted in a secure way. Precise if option is default, included option or an extra modules to buy.
Note : Options are present to set a minimum size for password, respect complexity like presence of numbers or special characters.
Note : 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.
Note : Does database process run as root/administrator or unprivileged user? What is default configuration?
Note : Is there a separate user to manage special operation like backup, security officer, administrator, etc.? Is it default or optional?
Note : Common Criteria certified product list.
Note : FirebirdSQL seems to only have SYSDBA user and DB owner. There are no separate roles for backup operator and security administrator.
Note : User can define a dedicated backup user but nothing particular in default install.
Note : Authentication methods.
Note : Informix Dynamic Server supports PAM and other configurable authentication. By default uses OS authentication.
Note : Authentication methods.
Note : With the use of Pervasive AuditMaster.
Note : User-based security is optional in Polyhedra, but when enabled can be enhanced to a role-based model with auditing.
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 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
-
SELECT * FROM default.foo
vs.SELECT * FROM alternate.foo
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 but 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. 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 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 recently added support for foreign schemas, which is the ability to import schemas from other servers as defined in ISO/IEC 9075-9. 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. 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.