Comparison of relational database management systems

The following tables compare general and technical information for a number ofrelational database management systems. Please see the individual products' articles for further information. This article is not all-inclusive or necessarily up-to-date. Unless otherwise specified in footnotes, comparisons are based on the stable versions without any add-ons, extensions or external programs.

Contents

[hide]

• 1General information
• 2Timeline
• 3Operating system support
• 4Fundamental features
• 5Limits
• 6Tables and views
• 7Indexes
• 8Database capabilities
• 9Data types
• 10Other objects
• 11Partitioning
• 12Access control
• 13Databases vs schemas (terminology)
• 14See also
• 15References
• 16External links

[edit]General information

MaintainerFirst public release dateLatest stable versionLatest release dateSoftware license4D (4th Dimension)4D s.a.s1984v12.2 SQL ProprietaryADABASSoftware AG19708.1 ProprietaryAdaptive Server EnterpriseSybase198715.5 ProprietaryAdvantage Database Server (ADS)Sybase199210.12010-12ProprietaryAltibaseAltibase Corp.^[1]2000-075.1.1 ProprietaryApache DerbyApache200410.8.1.22011-05-02Apache LicenseCUBRIDNHN Corporation^[2]2008-118.4.02011-05-12GPL v2DatacomCA, Inc.?11.2 ProprietaryDB2IBM19839.72009-04-22ProprietaryDrizzleBrian Aker2008Build 1126 BSD,GPL v2Empress Embedded DatabaseEmpress Software Inc^[3]197910.202010-03ProprietaryFileMakerFileMaker^[4]198411.02010-03ProprietaryFirebirdFirebird project^[5]2000-07-252.52010-10-04IPL^[6] and IDPL^[7]FrontBaseFrontBase, Inc^[8]19965.1.22010-01ProprietaryHSQLDBHSQL Development Group20012.2.52011-07BSDH2H2 Software20051.3.1542011-04-04EPL and modifiedMPLInformix Dynamic ServerIBM198011.70.xC22011-03-28ProprietaryIngresIngres Corp.1974Ingres Database 102010-10-12GPL andProprietaryInterBaseEmbarcadero1984InterBase XE2010-09-21ProprietaryLinter SQL RDBMSRELEX Group19906.x ProprietaryLucidDBThe Eigenbase Project^[9]2007-010.9.3 GPL v2MaxDBSAP AG2003-057.62008-01ProprietaryMicrosoft Access (JET)Microsoft199214 (2010) ProprietaryMicrosoft Visual FoxproMicrosoft1984^[10]9 (2005)2007-10-11^[10]ProprietaryMicrosoft SQL ServerMicrosoft19892008 R2 (v10.5) ProprietaryMicrosoft SQL Server Compact (Embedded Database)Microsoft20002010 (v3.5 SP2) ProprietaryMonetDBThe MonetDB Developer Team20045.222010-10MonetDB Public License v1.1^[11]mSQLHughes Technologies19943.8^[12]2006-06-09ProprietaryMySQLSun Microsystems (nowOracle Corporation)1995-115.5.82010-12-15GPL orProprietaryNavibaseNaviworx20091.0.02010-11-02ProprietaryNexusdbNexus Database Systems Pty Ltd^[13]2003-093.042010-05-08ProprietaryHP NonStop SQLHewlett-Packard1987SQL/MX 2.3 ProprietaryOmnis StudioTigerLogic Inc^[14]1982-074.3.1 Release 1no2008-05ProprietaryOpenBase SQLOpenBase International^[15]199111.0.0 ProprietaryOracleOracle Corporation1979-1111g Release 22009-09ProprietaryOracle RdbOracle Corporation19847.2.5.02011-06-20^[16]ProprietaryOpenEdgeProgress Software Corporation198410.2B ProprietaryOpenLink VirtuosoOpenLink Software^[17]19986.22010-09GPL orProprietaryParadoxCorel Corporation^[18]1985112003ProprietaryPervasive PSQLPervasive Software1982112010-09ProprietaryPolyhedra DBMSENEA AB19938.42010-12ProprietaryPostgreSQLPostgreSQL Global Development Group^[19]1989-069.0.4^[20]2011-04-18PostgreSQL licence (Free and Open Source)^[21]R:BaseR:BASE Technologies^[22]19827.6 ProprietaryRDM EmbeddedRaima Inc.^[23]198410 ProprietaryRDM ServerRaima Inc.^[23]19908.3 ProprietaryScimoreDBScimore^[24]20053.02008-03-03ProprietarySmallSQLSmallSQL2005-04-160.202008-12LGPLSQL AnywhereSybase199212.02010-07-09ProprietarySQLBaseUnify Corp.^[25]198211.52008-11ProprietarySQLiteD. Richard Hipp2000-08-173.7.6.32011-05-19^[26]Public domainSuperbaseSuperbase1984Scientific (2004) ProprietaryTeradataTeradata198413.10 ProprietaryUniDataRocket Software19887.2.102011-04ProprietaryUniVerseRocket Software198511.1.32011-06Proprietary

[edit]Timeline

Timeline of the development of major RDBMS software:

[edit]Operating system support

The operating systems the RDBMSes can run on.

WindowsMac OS XLinuxBSDUNIXAmigaOSSymbianz/OS¹4th DimensionYesYesNoNoNoNoNoNoADABASYesNoYesNoYesNoNoYesAdaptive Server EnterpriseYesNoYesYesYesNoNoNoAdvantage Database ServerYesNoYesNoNoNoNoNoAltibaseYesNoYesNoYesNoNoNoApache Derby²YesYesYesYesYesNoNoYesCUBRIDYesPartial¹⁰YesNoNoNoNoNoDrizzleNoYesYesYesYesNoNoNoDB2⁵YesYes (Express C)YesNoYesNoNoYesEmpress Embedded DatabaseYesYesYesYesYesNoNoNoFirebirdYesYesYesYesYesNoNoMaybeHSQLDB²YesYesYesYesYesNoNoYesH2²YesYesYesYesYesNoNoYesFileMakerYesYesNoNoNoNoNoNoInformix Dynamic ServerYesYesYesYesYesNoNoYesIngresYesYesYesYesYesNoNoPartialInterBaseYesYesYesNoYes (Solaris)NoNoNoLinter SQL RDBMS⁶YesYesYesYesYes⁶NoNoNoLucidDBYesYesYesNoNoNoNoNoMaxDBYesNoYesNoYesNoNoMaybeMicrosoft Access (JET)YesNoNoNoNoNoNoNoMicrosoft Visual FoxproYesNoNoNoNoNoNoNoMicrosoft SQL ServerYesNoNoNoNoNoNoNoMicrosoft SQL Server Compact (Embedded Database)YesNoNoNoNoNoNoNoMonetDBYesYesYesNoYesNoNoNoMySQL⁸YesYesYesYesYesYesYesYesNavibasePartialYesPartialPartialNoNoNoNoOmnis StudioYesYesYesNoNoNoNoNoOpenBase SQLYesYesYesYesYesNoNoNoOracle⁴YesYesYesNoYesNoNoYesOracle Rdb³NoNoNoNoNoNoNoOpenEdgeYesNoYesNoYesNoNoNoOpenLink VirtuosoYesYesYesYesYesNoNoYesPervasive PSQLYesYes (OEM only)YesNoNoNoNoNoPolyhedra⁷YesNoYesNoYesNoNoNoPostgreSQLYesYesYesYesYesNoNoNoR:BaseYesNoNoNoNoNoNoNoRDM EmbeddedYesYesYesYesYesNoNoNoRDM ServerYesYesYesYesYesNoNoNoScimoreDBYesNoNoNoNoNoNoNoSmallSQL²YesYesYesYesYesNoNoYesSQL AnywhereYesYesYesNoYesNoNoNoSQLBaseYesNoYesNoNoNoNoNoSQLiteYesYesYesYesYesYesYesMaybeSuperbaseYesNoNoNoNoYesNoNoTeradataYesNoYesNoYesNoNoNoUniDataYesNoYesNoYesNoNoNoUniVerseYesNoYesNoYesNoNoNo

Note (1): Open source databases listed as UNIX-compatible will likely compile and run under z/OS’s built-in UNIX System Services (USS) subsystem. Most databases listed as Linux-compatible can run alongside z/OS on the same server usingLinux on zSeries.

Note (2): The database availability depends on Java Virtual Machine not on the operating system

Note (3): Oracle Rdb was originally developed byDEC, and runs on OpenVMS

Note (4): Oracle database 11g also runs on OpenVMS, HP/UX and AIX. Mac OS X is limited to 10gR2. 10g also supported BS2000/OSD and z/OS (31-bit), but that support has been discontinued in 11g. Earlier versions than 10g were available on a wide variety of platforms.

Note (5): DB2 is also available for i5/OS, z/VM, z/VSE. Previous versions were also available for OS/2.

Note (6): Linter SQL RDBMS also runs onOpenVMS, Solaris, QNX, OS9000 and OS9.

Note (7): Polyhedra also runs onAIX,OSE, Solaris, LynxOS andVxWorks. Previous versions also ran onUltrix, VMS and pSOS. Source code kits allow customers to port to other platforms.

Note (8): MySQL also runs onSolaris, Opensolaris, and can be made from source on other platforms as well.

Note (9): Binaries are not yet available forMac OS X andBSD.

Note (10): CUBRID provides a client interface of its RDBMS forMac OS X called the CUBRID Manager, which can be used for remote CUBRID connection.

[edit]Fundamental features

Information about what fundamental RDBMS features are implemented natively.

MySQL InnoDB is ACID compliant

ACIDReferential integrityTransactionsUnicodeInterface4th DimensionYesYesYesYesGUI &SQLADABASYesNoYesYesproprietary direct call & SQL (via 3rd party)Adaptive Server EnterpriseYesYesYesYesSQLAdvantage Database ServerYesYesYesYes³API &SQLAltibaseYesYesYes?SQLApache DerbyYesYesYesYesSQLCUBRIDYesYesYesYesGUI &SQLDrizzleYesYesYesYesSQLDB2YesYesYesYesGUI &SQLEmpress Embedded DatabaseYesYesYesYesAPI &SQLFirebirdYesYesYesYesSQLHSQLDBYesYesYesYesSQLH2YesYesYesYesSQLInformix Dynamic ServerYesYesYesYesSQLIngresYesYesYesYesSQL & QUELInterBaseYesYesYesYesSQLLinter SQL RDBMSYesYesYesYesGUI &SQLLucidDBYesNoNoYesSQLMaxDBYesYesYesYesSQLMicrosoft Access (JET)YesYesYesYesGUI &SQLMicrosoft Visual FoxProNoYesYesNoGUI &SQLMicrosoft SQL ServerYesYesYesYesGUI &SQLMicrosoft SQL Server Compact (Embedded Database)YesYesYesYesGUI &SQLMonetDBYesYesYesYes?MySQLYes²Yes²Yes² except forDDL ^[27]YesSQLNavibaseYesYesYesYesAPI &GUI & SQLOpenBase SQLYesYesYesYesGUI &SQLOracleYesYesYes except for DDL ^[27]YesAPI &GUI & SQLOracle RdbYesYesYesYesSQLOpenLink VirtuosoYesYesYesYesAPI &GUI & SQLPolyhedra DBMSYesYesYesYesSQLPostgreSQLYesYesYesYesGUI &SQLRDM EmbeddedYesYesYesYesSQL & APIRDM ServerYesYesYesYesSQL & APIScimoreDBYesYesYesPartialSQLSQL AnywhereYesYesYesYesSQLSQLBaseYesYesYesYesAPI &GUI & SQLSQLiteYesYesYesOptional^[28]SQLTeradataYesYesYesYesSQLUniDataYesNoYesYesMultipleUniVerseYesNoYesYesMultiple ACIDReferential integrityTransactionsUnicodeInterface

Note (1): Currently only supports read uncommited transaction isolation. Version 1.9 adds serializable isolation and version 2.0 will be fully ACID compliant.

Note (2): For ACID compliance with MySQL, the InnoDB storage engine must be chosen.^[29][30]

Note (3): Support for Unicode is new in version 10.0.

[edit]Limits

Information about data size limits.

Max DB sizeMax table sizeMax row sizeMax columns per rowMax Blob/Clob sizeMax CHAR sizeMax NUMBER sizeMin DATE valueMax DATE valueMax column name size4th Dimensionlimited ? ?65135200 GB (2 GiBUnicode)200 GB (2 GiBUnicode)64 bits ? ? ?Advantage Database ServerUnlimited16 EiB65530 B65135 / (10+ AvgFieldNameLength)4 GiB ?64 bits ? ?128Apache DerbyUnlimitedUnlimitedUnlimited1012 (5000 in views)2 147 483 647 chars254 (VARCHAR: 32672) ?0001-01-019999-12-31128CUBRID2 EB2 EBUnlimited6400Unlimited1 GB64 bits0001-01-019999-12-31254DrizzleUnlimited64 TB8 kB10004 GB (longtext, longblob)64 kB (text)64 bits0001999964DB2512 TiB512 TB32 677 B10122 GB32 KiB)64 bits00019999128Empress Embedded DatabaseUnlimited2⁶³-1 bytes2 GB327672 GB2 GB64 bits0000-01-019999-12-3132FirebirdUnlimited¹~32 TB65 536 BDepends on data types used.2 GB32 767 B64 bits1003276831HSQLDB64 TBUnlimited⁸Unlimited⁸Unlimited⁸64 TB⁷Unlimited⁸Unlimited⁸0001-01-019999-12-31128H264 TBUnlimited⁸Unlimited⁸Unlimited⁸64 TB⁷Unlimited⁸64 bits-9999999999999999Unlimited⁸Informix Dynamic Server~128 PB~128 PB32 765 bytes (exclusive of large objects)327654 TB3276510³²01/01/0001¹⁰12/31/9999128 bytesIngresUnlimitedUnlimited256 kB10242 GB32 000 B64 bits0001999932InterBaseUnlimited¹~32 TB65 536 BDepends on data types used.2 GB32 767 B64 bits1003276831Linter SQL RDBMSUnlimited2³⁰ rows64 kB (w/o BLOBs), 4 GB (BLOB)2504 GB4 kB64 bits0001-01-012099-12-31128Microsoft Access (JET)2 GB2 GB16 MB25564 kB (memo field), 1 GB ("OLE Object" field)255 B (text field)32 bits0100999964Microsoft Visual FoxproUnlimited2 GB65 500 B2552 GB16 MB32 bits00019999 ?Microsoft SQL Server524 258 TB (32 767 files * 16 TB max file size)524 258 TBUnlimited300002 GB2 GB⁶126 bits²00019999128Microsoft SQL Server Compact (Embedded Database)4 GB4 GB8060 bytes1024500 MB4000126 bits ²00019999128MySQL 5UnlimitedMyISAM storage limits: 256 TB; Innodb storage limits: 64 TB64 kB³4096⁴4 GB (longtext, longblob)64 kB (text)64 bits1000999964OracleUnlimited (4 GB * block size per tablespace)4 GB * block size (with BIGFILE tablespace)8 kB1000Unlimited4000 B126 bits-4712999930PolyhedraLimited by available RAM, address space2³² rowsUnlimited655364 GB (subject to RAM)4 GB (subject to RAM)32 bits0001-01-018000-12-31255PostgreSQLUnlimited32 TB1.6 TB250-1600 depending on type1 GB (text, bytea) - stored inline or 2 GB (stored in pg_largeobject)1 GBUnlimited-4713587489763ScimoreDBUnlimited16 EB8050 B25516 TB8000 B64 bits ? ? ?SQL Anywhere104 TB (13 files, each file up to 8 TB (32k pages))Limited by file sizeLimited by file size450002 GB2 GB64 bits0001-01-019999-12-31 ?SQLite32 TB (2³⁰ pages * 32 kB max page size) ? ?327671 GB1 GB64 bitsNo DATE type⁹No DATE type⁹ ?TeradataUnlimitedUnlimited64 kB wo/lobs (64 GB w/lobs)20482 GB10 00064 bits ?9999-12-31 Select 80991231 (date);30UniVerseUnlimitedUnlimitedUnlimitedUnlimitedUnlimitedUnlimitedUnlimitedUnlimitedUnlimitedUnlimited Max DB sizeMax table sizeMax row sizeMax columns per rowMax Blob/Clob sizeMax CHAR sizeMax NUMBER sizeMin DATE valueMax DATE valueMax column name size

Note (1): Firebird 2.x maximum database size is effectively unlimited with the largest known database size >980 GB.^[31] Firebird 1.5.x maximum database size: 32 TB.

Note (2): limit is 10³⁸usingDECIMAL datatype^[32]

Note (3): InnoDB is limited to 8,000 bytes (excludingVARBINARY, VARCHAR, BLOB, or TEXT columns)^[33]

Note (4): InnoDB is limited to 1,000 columns^[33]

Note (6): UsingVARCHAR (MAX) in SQL 2005 and later

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 (2³¹) 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,^[34] which work for timestamps between 0000-01-01 00:00:00 and 5352-11-01 10:52:47.

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.

[edit]Tables and views

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

Temporary tableMaterialized view4th DimensionYesPlanned for inclusion in next major releaseADABAS??Adaptive Server EnterpriseYes¹NoAdvantage Database ServerYesNo (only common views)AltibaseYesYesApache DerbyYesNoCUBRIDNoNoDrizzleYesNo⁴DB2YesYesEmpress Embedded DatabaseYesYesFirebirdYesNo (only common views)HSQLDBYesNoH2YesNoInformix Dynamic ServerYesNo²IngresYesPlanned for inclusion in next major releaseInterBaseYesNoLinter SQL RDBMSYesNoLucidDBNoNoMaxDBYesNoMicrosoft Access (JET)NoNoMicrosoft Visual FoxproYesYesMicrosoft SQL ServerYesYes³Microsoft SQL Server Compact (Embedded Database)YesNoMonetDBYesNoMySQLYesNo⁴OpenBase SQLYesYesOracleYesYesOracle RdbYesYesOpenLink VirtuosoYesYesPolyhedra DBMSNoNo (only common views)PostgreSQLYesNo⁵SQL AnywhereYesYesScimoreDBNoNoSQLiteYesNoTeradataYesYesUniDataYesNoUniVerseYesNo

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

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.^[36]

Note (3):Query optimizer support only in Developer and Enterprise Editions. In other versions, a direct reference to materialized view and a query hint are required.^[37]

Note (4): Materialized views can be emulated usingstored procedures and triggers.^[38]

Note (5): Materialized views can be emulated with stored procedures and triggers usingPL/pgSQL, PL/Perl, PL/Python, or other procedural languages.^[39]

[edit]Indexes

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

R-/R+ treeHashExpressionPartialReverseBitmapGiSTGINFull-textSpatialFOT4th Dimension?Cluster????????ADABAS??????????Adaptive Server EnterpriseNoNoYesNoYesNoNoNoYes?Advantage Database ServerNoNoYesNoYesYesNoNoYes?Apache DerbyNoNoNoNoNoNoNoNoNo^[40]?CUBRIDNoNoNoNoYesNoNoNo??DrizzleNoNoNoNoNoNoNoNoNo?DB2No?YesNoYesYesNoNoYes^[41]?Empress Embedded DatabaseYesNoNoYesNoYesNoNoNo?FirebirdNoNoYesNoYes ¹NoNoNoNo^[42]?HSQLDBNoNoNoNoNoNoNoNoNo?H2NoYesNoNoNoNoNoNoYes^[43]?Informix Dynamic ServerYesYesYesYesYesYesYesYesYesYesYesIngresYesYesIngres v10NoNoIngres v10NoNoNo?InterBaseNoNoNoNoNoNoNoNoNo?Linter SQL RDBMS¹⁰NoNoNoNoNoNoNoNoYes^[44]?LucidDBNoNoNoNoNoYesNoNoNo?MaxDBNoNoNoNoNoNoNoNoNo?Microsoft Access (JET)NoNoNoNoNoNoNoNoNo^[45]?Microsoft Visual FoxproNoNoYesYesYes²YesNoNoNo?Microsoft SQL Server?Non/Cluster & fill factorYes³Yes⁴No³NoNoNoYes^[46]Yes^[47]Microsoft SQL Server Compact (Embedded Database)NoNoNoNoNoNoNoNoNo^[48]?MonetDBNoYesNoNoNoNoNoNo??MySQLMyISAM tables onlyMEMORY, Cluster (NDB), InnoDB,⁵ tables onlyNo^[49]NoNoNoNoNoMyISAM tables only^[50]?OracleYes ¹¹Cluster TablesYesYes ⁶YesYesNoNoYes^[51]Yes^[52]Oracle RdbNoYes?NoNo?NoNo??OpenLink VirtuosoYesClusterYesNoNoYesNoNoYes?Polyhedra DBMSNoYesNoNoNoNoNoNo??PostgreSQLYesYesYesYesYes⁷Yes⁸YesYesYes^[53]Postgis^[54]ScimoreDBNoNoNoNoNoNoNoNoYes^[55]?SQL AnywhereNoNoNoNoNoNoNoNoYes?SQLiteYesNoNoNoYesNoNoNoYes^[56]SpatiaLite^[57]TeradataNoYesYesYesNoYesNoNo?^[58]?UniVerseYesYesYes³Yes³Yes³NoNoNo?? R-/R+ treeHashExpressionPartialReverseBitmapGiSTGINFull-textSpatial

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

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

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

Note (4): Can be implemented by using an indexed view.^[63]

Note (5): InnoDB automatically generates adaptive hash index^[64] 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 (8): PostgreSQL will likely support on-disk bitmap indexes in a future version. Version 8.2 supports a related technique known as "in-memory bitmap scans".

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

[edit]Database capabilities

UnionIntersectExceptInner joinsOuter joinsInner selectsMerge joinsBlobs andClobsCommon Table ExpressionsWindowing FunctionsParallel Query4th DimensionYesYesYesYesYesNoNoYes???ADABASYes??????????Adaptive Server EnterpriseYes??YesYesYesYesYes??YesAdvantage Database ServerYesNoNoYesYesYesYesYes?No?AltibaseYes??YesYesYesYesYes???Apache DerbyYesYesYesYesYes??YesNoNo?CUBRIDYesYesYesYesYesYesYesYesNoNo?DrizzleYesNoNoYesYesYesNoYesNoNoNo^[65]DB2YesYesYesYesYesYesYesYesYesYesYes^[66]Empress Embedded DatabaseYesYesYesYesYesYesYesYes???FirebirdYes??YesYesYesYesYesYesYes?HSQLDBYesYesYesYesYesYesNoYesYesNoNoH2YesYesYesYesYesYesNoYesexperimental^[67]No^[68]?Informix Dynamic ServerYes?Yes, via MINUSYesYesYesYesYesYes?Yes^[69]IngresYesNoNoYesYesYesYesYesNoNo?InterBaseYes??YesYes??Yes???Linter SQL RDBMSYesYesYesYesYesYesYesYesNoYes?LucidDBYesYesYesYesYesYesYesNo???MaxDBYes??YesYesYesNoYes???Microsoft Access (JET)YesNoNoYesYesYesNoYesNoNo?Microsoft Visual FoxproYes??YesYesYes?Yes???Microsoft SQL ServerYesYes (2005 and beyond)Yes (2005 and beyond)YesYesYesYesYesYesYesYes^[70]Microsoft SQL Server Compact (Embedded Database)YesNoNoYesYes?NoYesNoNo?MonetDB???????????MySQLYesNoNoYesYesYesNoYesNo^[71]NoNo^[72]OpenBase SQLNoNoNoYesYesYesYesYes???OracleYesYesYes, via MINUSYesYesYesYesYesYes ¹YesYes^[73]Oracle RdbYes??YesYesYesYesYes???OpenLink VirtuosoYes??YesYesYes?Yes???Polyhedra DBMSYesYesYesYesNo??Yes???PostgreSQLYesYesYesYesYesYesYesYesYesYesNo^[74]ScimoreDBYes??YesLEFT onlyYesYesYes???SmallSQL???????????SQL AnywhereYesYesYesYesYesYesYesYesYesYes?SQLiteYesYesYesYesLEFT onlyYes?YesNoNo?TeradataYesYesYesYesYesYesYesYesNoYesYesUniVerseYesYesYesYesYesYesYesNoNoNo? UnionIntersectExceptInner joinsOuter joinsInner selectsMerge joinsBlobs andClobsCommon Table ExpressionsWindowing FunctionsParallel Query

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

[edit]Data types

Type systemIntegerFloating pointDecimalStringBinaryDate/TimeBooleanOtherCUBRID^[75]StaticSMALLINT (16-bit), INTEGER (32-bit), BIGINT (64-bit)FLOAT, REAL(32-bit), DOUBLE(64-bit)DECIMAL, NUMERICCHAR, VARCHAR, NCHAR, NVARCHAR, CLOBBLOBDATE, DATETIME, TIME, TIMESTAMPBITMONETARY, BIT VARYING, SET, MULTISET, SEQUENCEDrizzle^[76]StaticINT (32-bit), BIGINT (64-bit)DOUBLE (aka REAL) (64-bit)DECIMALBINARY, VARCHAR, VARBINARY, TEXT,BLOBDATETIME, DATE, TIMESTAMP ENUM, SERIALEmpress Embedded DatabaseStaticTINYINT, SQL_TINYINT or INTEGER8

SMALLINT, SQL_SMALLINT or INTEGER16 INTEGER, INT, SQL_INTEGER or INTEGER32 BIGINT, SQL_BIGINT or INTEGER64

REAL, SQL_REAL or FLOAT32

DOUBLE PRECISION, SQL_DOUBLE or FLOAT64 FLOAT or SQL_FLOAT EFLOAT

DECIMAL, DEC, NUMERIC, SQL_DECIMAL or SQL_NUMERIC

DOLLAR

CHARACTER,

ECHARACTER, CHARACTER VARYING, NATIONAL CHARACTER, NATIONAL CHARACTER VARYING and NLSCHARACTER

CHARACTER LARGE OBJECT, TEXT, NATIONAL CHARACTER LARGE OBJECT, and NLSTEXT

BINARY LARGE OBJECT or BLOB

BULK

DATE,

EDATE, TIME, ETIME, EPOCH_TIME, TIMESTAMP, MICROTIMESTAMP

BOOLEANSEQUENCE 32

SEQUENCE

HSQLDB^[77]StaticTINYINT (8-bit), SMALLINT (16-bit), INTEGER (32-bit), BIGINT (64-bit)DOUBLE (64-bit)DECIMAL, NUMERICCHAR, VARCHAR, LONGVARCHAR, CLOBBINARY, VARBINARY, LONGVARBINARY, BLOBDATE, TIME, TIMESTAMP, INTERVALBOOLEANOTHER (object), BIT, BIT VARYING, ARRAYInformix Dynamic Server^[78]StaticSMALLINT (16-bit), INT (32-bit), INT8 (64-bit proprietary), BIGINT (64-bit)SMALLFLOAT (32-bit), FLOAT (64-bit)DECIMAL (32 digits float/fixed), MONEYCHAR, VARCHAR, NCHAR, NVARCHAR, LVARCHAR, CLOB, TEXTTEXT, BYTE, BLOB, CLOBDATE, DATETIME, INTERVALBOOLEANSET, LIST, MULTISET, ROW, TIMESERIES, SPATIAL, USER DEFINED TYPESIngres^[79]StaticTINYINT (8-bit), SMALLINT (16-bit), INTEGER (32-bit), BIGINT (64-bit)FLOAT4 (32-bit), FLOAT (64-bit)DECIMALC, CHAR, VARCHAR, LONG VARCHAR, NCHAR, NVARCHAR, LONG NVARCHAR, TEXTBYTE, VARBYTE, LONG VARBYTE (BLOB)DATE, ANSIDATE, INGRESDATE, TIME, TIMESTAMP, INTERVALN/AMONEY, OBJECT_KEY, TABLE_KEY, USER-DEFINED DATA TYPES (via OME)Microsoft SQL Server^[80]StaticTINYINT, SMALLINT, INT, BIGINTFLOAT, REALNUMERIC, DECIMAL, SMALLMONEY, MONEYCHAR, VARCHAR, TEXT, NCHAR, NVARCHAR, NTEXTBINARY, VARBINARY, IMAGE, FILESTREAMDATE, DATETIMEOFFSET, DATETIME2, SMALLDATETIME, DATETIME, TIMEBITCURSOR, TIMESTAMP, HIERARCHYID, UNIQUEIDENTIFIER, SQL_VARIANT, XML, TABLEMicrosoft SQL Server Compact (Embedded Database)^[81]StaticTINYINT, SMALLINT, INT, BIGINTFLOAT, REALNUMERIC, DECIMAL, MONEYNCHAR, NVARCHAR, NTEXTBINARY, VARBINARY, IMAGEDATETIMEBITTIMESTAMP, ROWVERSION, UNIQUEIDENTIFIER, IDENTITY, ROWGUIDCOLMySQL^[82]StaticTINYINT (8-bit), SMALLINT (16-bit), MEDIUMINT (24-bit), INT (32-bit), BIGINT (64-bit)FLOAT (32-bit), DOUBLE (aka REAL) (64-bit)DECIMALCHAR, BINARY, VARCHAR, VARBINARY, TEXT, TINYTEXT, MEDIUMTEXT, LONGTEXTTINYBLOB, BLOB, MEDIUMBLOB, LONGBLOBDATETIME, DATE, TIMESTAMP, YEARBOOLEAN (aka BOOL) = synonym for TINYINTENUM, SET, GIS data types (Geometry, Point, Curve, LineString, Surface, Polygon, GeometryCollection, MultiPoint, MultiCurve, MultiLineString, MultiSurface, MultiPolygon)Oracle^[83]Static + Dynamic (through ANYDATA)NUMBERBINARY_FLOAT, BINARY_DOUBLENUMBERCHAR, VARCHAR2, CLOB, NCLOB, NVARCHAR2, NCHARBLOB, RAW, LONGRAW, BFILEDATE, TIMESTAMP (with/without TIMEZONE), INTERVALN/ASPATIAL, IMAGE, AUDIO, VIDEO, DICOM, XMLTypePolyhedraStaticINTEGER8 (8-bit), INTEGER(16-bit), INTEGER (32-bit)FLOAT32 (32-bit), FLOAT (aka REAL; 64-bit)N/AVARCHAR, LARGE VARCHAR (aka CHARACTER LARGE OBJECT)LARGE BINARY (aka BINARY LARGE OBJECT)DATETIMEBOOLEANN/APostgreSQL^[84]StaticSMALLINT (16-bit), INTEGER (32-bit), BIGINT (64-bit)REAL (32-bit), DOUBLE PRECISION (64-bit)DECIMAL, NUMERICCHAR, VARCHAR, TEXTBYTEADATE, TIME (with/without TIMEZONE), TIMESTAMP (with/without TIMEZONE), INTERVALBOOLEANENUM, POINT, LINE, LSEG, BOX, PATH, POLYGON, CIRCLE, CIDR, INET, MACADDR, BIT, UUID, XML, arraysSQLite^[85]DynamicINTEGER (64-bit)REAL (aka FLOAT, DOUBLE) (64-bit)N/ATEXT (aka CHAR, CLOB)BLOBN/AN/AN/AUniDataDynamicN/AN/AN/AN/AN/AN/AN/AN/AUniVerseDynamicN/AN/AN/AN/AN/AN/AN/AN/A Type systemIntegerFloating pointDecimalStringBinaryDate/TimeBooleanOther

[edit]Other objects

Information about what other objects are supported natively.

Data DomainCursorTriggerFunction ¹Procedure ¹External routine ¹4th DimensionYesNoYesYesYesYesADABAS?Yes?Yes?Yes??Adaptive Server EnterpriseYesYesYesYesYesYesAdvantage Database ServerYesYesYesYesYesYesApache DerbyNoYesYesYes ²Yes ²Yes ²CUBRIDYesYesYesYesYes ²YesDrizzleYesYesYes ⁴Yes ⁴Yes ⁴Yes ⁴Empress Embedded DatabaseYes via RANGE CHECKYesYesYesYesYesDB2Yes via CHECK CONSTRAINTYesYesYesYesYesFirebirdYesYesYesYesYesYesHSQLDBYesNoYesYesYesYesH2YesNoYes ²Yes ²Yes ²YesInformix Dynamic ServerYes via CHECKYesYesYesYesYesIngresYesYesYesYesYesYesInterBaseYesYesYesYesYesYesLinter SQL RDBMSNoYesYesYesYesNoLucidDBNoYesNoYes ²Yes ²Yes ²MaxDBYesYesYesYesYes?Microsoft Access (JET)YesNoNoNoYes, But single DML/DDL OperationYesMicrosoft Visual FoxproNoYesYesYesYesYesMicrosoft SQL ServerYes (2000 and beyond)YesYesYesYesYesMicrosoft SQL Server Compact (Embedded Database)NoYesNoNoNoNoMonetDBNoNoYesYesYesYesMySQLNo  ³YesYesYesYesYesOpenBase SQLYesYesYesYesYesYesOracleYesYesYesYesYesYesOracle RdbYesYesYesYesYesYesOpenLink VirtuosoYesYesYesYesYesYesPolyhedra DBMSNoNoYesYesYesYesPostgreSQLYesYesYesYesYesYesScimoreDBNoNoNoNoYesYesSQL AnywhereYesYesYesYesYesYesSQLiteNoNoYesNoNoYesTeradataNoYesYesYesYesYesUniDataNoNoYesYesYesYesUniVerseNoNoYesYesYesYes Data DomainCursorTriggerFunction ¹Procedure ¹External routine ¹

Note (1): Bothfunction and procedure refer to internal routines written in SQL and/or procedural language likePL/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 codefunctions and procedures in Java.

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

Note (4): In Drizzle the user codesfunctions and procedures in C++.

[edit]Partitioning

Information about what partitioning methods are supported natively.

RangeHashComposite (Range+Hash)ListNative Replication API4th Dimension?????ADABAS?????Adaptive Server EnterpriseYesYesNoYes?Advantage Database ServerNoNoNoNoYesApache DerbyNoNoNoNo?CUBRIDYesYesNoYes?IBM DB2YesYesYesYes?Empress Embedded DatabaseNoNoNoNoYesFirebirdNoNoNoNoNoHSQLDBNoNoNoNoNoH2NoNoNoNoNoInformix Dynamic ServerYesYesYesYesYesIngresYesYesYesYesNoInterBaseNoNoNoNoYesLinter SQL RDBMSNoNoNoNoNoMaxDBNoNoNoNo?Microsoft Access (JET)NoNoNoNoYesMicrosoft Visual FoxproNoNoNoNoNoMicrosoft SQL ServerYesNoNoNo?Microsoft SQL Server Compact (Embedded Database)NoNoNoNoYesMonetDBYes (M5)Yes (M5)Yes (M5)No?MySQLYesYesYesYes?OpenBase SQL?????OracleYesYesYesYes?Oracle RdbYesYes???OpenLink VirtuosoYesNoNoNo?Polyhedra DBMSNoNoNoNoNoPostgreSQLYes¹Yes¹Yes¹Yes¹?ScimoreDBNoYesNoNoYesSQL AnywhereNoNoNoNo?SQLiteNoNoNoNo?TeradataYesYesYesYes?UniVerseYesYesYesYesYes RangeHashComposite (Range+Hash)ListNative Replication API

Note (1): PostgreSQL 8.1 provides partitioning support through check constraints. Range, List and Hash methods can be emulated with PL/pgSQL or other procedural languages.^[86]

[edit]Access control

Information about access control functionalities (work in progress).

Native network encryption¹Brute-force protectionEnterprise directory compatibilityPassword complexity rules²Patch access³Run unprivileged⁴AuditResource limitSeparation of duties (RBAC)⁵Security CertificationAdaptive Server EnterpriseYes (optional; to pay)YesYes (optional ?)YesPartial (need to register; depend on which product)^[87]YesYesYesYesYes (EAL4+ ¹)Advantage Database ServerYesNoNoNo?YesNoNoYes?DB2Yes?Yes (LDAP, Kerberos…)Yes?YesYesYesYesYes (EAL4+⁶)Empress Embedded Database??NoNoYesYesYesNoYesNoFirebirdNoYes^[88]Yes (Windows trusted authenification)NoPartial (no security page)^[89]YesNoNoNo⁷?HSQLDBYesNoNoNoYesYesNoNoYesNoH2YesYes?No?Yes?YesYesNoInformix Dynamic ServerYes?Yes¹⁰?¹⁰YesYesYesYesYes?Linter SQL RDBMSYes (with SSL)YesNoYes (length only)NoYesYesYesYesYesMySQLYes (SSL with 4.0)NoYes (with 5.5)NoPartial (no security page)^[90]Yes???⁸NoOpenBase SQLYes?Yes (Open Directory, LDAP)No??????Microsoft SQL ServerYes?Yes (Microsoft Active Directory)YesYesYesYes (From 2008)YesYesYes (EAL1+¹)Microsoft SQL Server Compact (Embedded Database)No (not relevant, only file permissions)No (not relevant)No (not relevant)No (not relevant)YesYes (file access)YesYesNo?OracleYesYesYesYes?YesYesYesYesYes (EAL4+¹)PostgreSQLYesNoYes (LDAP, Kerberos…⁹)Yes (as of 9.0 with passwordcheck module)Yes^[91]YesNoYesNoYes (EAL1¹)SQL AnywhereYes?Yes (Kerberos)Yes?YesYesNoYesYes (EAL3+¹ as Adaptive Server Anywhere)SQLiteNo (not relevant, only file permissions)No (not relevant)No (not relevant)No (not relevant)Partial (no security page)^[92]Yes (file access)YesYesNoNo Native network encryption¹Brute-force protectionEnterprise directory compatibilityPassword complexity rules²Patch access³Run unprivileged⁴AuditResource limitSeparation of duties (RBAC)⁵Security Certification

Note (1): Network traffic could be transmitted in a secure way (not clear-text, en 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^[93]

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^[94]

Note (9): Authentication methods^[95]

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

[edit]Databases vs schemas (terminology)

This section may contain original research. Please improve it by verifying the claims made and adding references. Statements consisting only of original research may be removed. More details may be available on thetalk page. (June 2010)

The SQL specification makes clear what an "SQL schema" is; however, different databases implement it incorrectly. To compound this confusion the functionality can, when incorrectly implemented, overlap with that of the parent-database. An SQL schema is simply a namespace within a database, things within this namespace are addressed using the memberoperator dot ".". This seems to be a universal amongst all of the implementations.

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

Now, the issue, 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 db1.foo vs. SELECT * FROM db2.foo (no explicit schema between db and table)
• SELECT * FROM [db1.]default.foo vs. SELECT * FROM [db1.]alternate.foo (no explicit db 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 Postgres-schemas, insomuch as Postgres lacks off-the-shelf cross-database functionality 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 thatCREATE SCHEMA and CREATE DATABASE are analogs. It can therefore be said that MySQL has implemented cross-table functionality, skipped schema functionality entirely, and provided similar functionality into their implementation of a database. In summary, Postgres fully supports schemas but lacks some functionality MySQL has with databases, while MySQL does not even attempt to support true 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 Oracle 'shared-everything' 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 server. In the Oracle view, the '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.

The end result is confusion between the database factions. The Postgres and Oracle communities maintain that one database is all that is needed for one project, per the definition of database. MySQL proponents maintain that schemas have no legitimate purpose when the functionality can be achieved with databases. Postgres adheres to the SQL specification, in a more intuitive fashion (bottom-up), while MySQL’spragmatic counterargument allows their users to get the job done while creating conceptual confusion.

[edit]See also