Comparison of relational database management systems: Difference between revisions

Revision as of 06:16, 15 August 2023

Revision as of 06:25, 15 August 2023

Line 1,813:

| 1,012 (5,000 in views)

| 2,147,483,647 chars

| 254 (<code>{{mono|VARCHAR</code>}}: 32,672)

| 64 bits

| 0001-01-01

Line 1,872:

| Unlimited

| 10,000

| {{N/A}}

| 2 MB

| 128 bits

Line 1,886:

| 4 GB

| 10,000,000

| 1 billion characters, {{tmath|10^{-400} }} to {{tmath|10^{400} }}, +-

| 0001-01-01

| 4000-12-31

Line 1,892:

|-

! style="text-align:left" | [[Firebird (database server)|Firebird]]

| Unlimited<sup id="limit_1_back">[[#limit 1|1]]</sup>

| ~32 TB

| 65,536 B

Line 2,009:

| 16 MB

| 255

| 64 KB (memo field), <br/>1 GB ("OLE Object" field)

| 255 B (text field)

| 32 bits

Line 2,029:

|-

! style="text-align:left" | [[Microsoft SQL Server]]

| 524,272 TB (32 767 files *&times; 16 TB max file size)

16ZB per instance

| 524,272 TB

Line 2,102:

|-

! style="text-align:left" | [[Oracle Database|Oracle]]

| {{val|2|u=PB}} (with standard 8k block)<br/>{{val|8|ul=PB}} (with max 32k block)<br/>{{val|8|u=EB}} (with max 32k block and BIGFILE option)

| 2PB (with standard 8k block)

8PB (with max 32k block)

8EB (with max 32k block and BIGFILE option)

| 4 GB * block size (with BIGFILE tablespace)

| 8 KB

Line 2,238 ⟶ 2,236:

|-

! style="text-align:left" | [[SQLite]]

| 128 TB (2³¹ pages *&times; 64 KB max page size)

| Limited by file size

| Limited by file size

Line 2,286 ⟶ 2,284:

|}

* <cite id="limit_1">[[#limit 1 back|Note (1):]]</cite> Firebird 2.x maximum database size is effectively unlimited with the largest known database size >980 GB.<ref>

{{Citation

| url = http://www.firebirdsql.org/index.php?op=guide&id=techspec

Line 2,298 ⟶ 2,296:

}}

</ref> Firebird 1.5.x maximum database size: 32 TB.

* <cite id="limit_2">[[#limit 2 back|Note (2):]]</cite> Limit is 10³⁸ using <code>DECIMAL</code> datatype.<ref>{{Citation

<cite id="limit_2">[[#limit 2 back|Note (2):]]</cite> Limit is 10³⁸ using <code>DECIMAL</code> datatype.<ref>{{Citation

| url = http://msdn.microsoft.com/en-us/library/ms187746.aspx

| publisher = Microsoft

Line 2,305 ⟶ 2,302:

| title = Library

}}</ref>

* <cite id="limit_3">[[#limit 3 back|Note (3):]]</cite> InnoDB is limited to 8,000 bytes (excluding <code>VARBINARY</code>, <code>VARCHAR</code>, <code>BLOB</code>, or <code>TEXT</code> columns).<ref name = "MySQL column count limit">{{Citation

<cite id="limit_3">[[#limit 3 back|Note (3):]]</cite> InnoDB is limited to 8,000 bytes (excluding <code>VARBINARY</code>, <code>VARCHAR</code>, <code>BLOB</code>, or <code>TEXT</code> columns).<ref name = "MySQL column count limit">{{Citation

| chapter-url = https://dev.mysql.com/doc/refman/8.0/en/column-count-limit.html

| publisher = Oracle

Line 2,313 ⟶ 2,309:

| chapter = Column count limit

}}</ref>

* <cite id="limit_4">[[#limit 4 back|Note (4):]]</cite> InnoDB is limited to 1,017 columns.<ref name = "MySQL column count limit" />

* <cite id="limit_4limit_6">[[#limit 46 back|Note (46):]]</cite> InnoDBUsing is<code>VARCHAR limited(MAX)</code> toin 1,017SQL columns2005 and later.<ref name = "MySQLSQL columnServer countRow-Overflow limit"Data /Exceeding 8 KB">{{Citation

<cite id="limit_6">[[#limit 6 back|Note (6):]]</cite> Using <code>VARCHAR (MAX)</code> in SQL 2005 and later.<ref name = "SQL Server Row-Overflow Data Exceeding 8 KB">{{Citation

| chapter-url = https://technet.microsoft.com/en-us/library/ms186981.aspx

| publisher = Microsoft

Line 2,324 ⟶ 2,318:

| chapter = Row-Overflow Considerations

}}</ref>

* <cite id="limit_7">[[#limit 7 back|Note (7):]]</cite> When using a page size of 32 KB, and when BLOB/CLOB data is stored in the database file.

* <cite id="limit_7limit_8">[[#limit 78 back|Note (78):]]</cite> WhenJava usingarray asize pagelimit sizeof 2,147,483,648 (2³¹) objects per array applies. This limit applies to number of 32characters in KBnames, androws whenper BLOB/CLOBtable, datacolumns isper storedtable, inand thecharacters databaseper file<code>CHAR</code>/<code>VARCHAR</code>.

* <cite id="limit_9">[[#limit 9 back|Note (9):]]</cite> Despite the lack of a date datatype, SQLite does include date and time functions,<ref>{{Citation

<cite id="limit_8">[[#limit 8 back|Note (8):]]</cite> 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 <code>CHAR</code>/<code>VARCHAR</code>.

<cite id="limit_9">[[#limit 9 back|Note (9):]]</cite> Despite the lack of a date datatype, SQLite does include date and time functions,<ref>{{Citation

| chapter-url = http://www.sqlite.org/lang_datefunc.html

| publisher = SQLite

Line 2,335 ⟶ 2,326:

| chapter = Date functions

}}</ref> which work for timestamps between 24 November 4714 B.C. and 1 November 5352.

* <cite id="limit_10">[[#limit 10 back|Note (10):]]</cite> 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.

* <cite id="limit_10limit_11">[[#limit 1011 back|Note (1011):]]</cite> InformixSince DATETIMEversion type has adjustable range from YEAR only through 1/10000th second12c. Earlier DATETIMEversions datesupport rangeup isto 0001-01-014000 00:00:00.00000 through 9999-12-31 23:59:59.99999B.

* <cite id="limit_12">[[#limit 12 back|Note (12):]]</cite> The 128PB{{val|128|u=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.

* <cite id="limit_11limit_13">[[#limit 1113 back|Note (1113):]]</cite> SinceInformix versionDECIMAL 12c.type Earliersupports versionsup supportto up32 decimal digits of precision with a range of {{tmath|10^{-130} }} to 4000{{tmath|10^{125} }}. Fixed and variable precision are Bsupported.

<cite id="limit_12">[[#limit 12 back|Note (12):]]</cite> 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.

<cite id="limit_13">[[#limit 13 back|Note (13):]]</cite> Informix DECIMAL type supports up to 32 decimal digits of precision with a range of 10^-130 to 10^125. Fixed and variable precision are supported.

==Tables and views==