This article is rated List-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||
|
Links from this article with broken #section links : You can remove this template after fixing the problems | FAQ | Report a problem |
What about adding a mention of the programming language(s) that each DBMS implementation uses?
The footnote for the MySQL DBMS support of ACID transactions says that the software will in some cases accept values outside a range specified in the data definition. I.e. .."violates the integrity [Consistency] clause"...
By my understanding of ACID compliance this is a blatant breach of the Consistency / Integrity clause of ACID compliance - i.e. that the transaction enforces the database is taken from one consistent state to another. If the data constraints are not enforced in the transaction and it is possible to commit values outside those constraints, surely the system is not ACID compliant. —Preceding unsigned comment added by 93.97.38.208 (talk) 15:14, 7 February 2010 (UTC)
I'm changing this to 'yes' with a footnote saying the same thing that is stated in the MySQL article, that ACID is supported only when using what is sometimes not the default storage engine. The listing should say which databases SUPPORT ACID. not which ones enforce it using any possible combinations of settings and in even the rarest exception cases. I think you would find a lot of other databases would not pass your strict interpretation either, and my interpretation is arguably of more use and interest to the reader (if someone is selecting which database to use for example).
LarsHolmberg (talk) 17:38, 19 August 2010 (UTC)
Lars: that doesn't make sense. What you're saying is akin to "this car can can go at 300mph, but you'll have to design and build a new engine to make it do that". I would say 'support' means that the product can do this, without one having to write their own storage engine to get it. Loads of RDMS's support ACID properly and out of the box by my interpretation - PostgreSQL, DB2 and Oracle being but a few popular ones. The simple fact is that because of the above problem with InnoDB not supporting ACID Consistency (and there being no other available and out of the box storage engines able to provide ACID compliance), MySQL cannot be said to support it. 93.97.38.208 (talk) 16:41, 21 February 2011 (UTC)
Filemaker Pro has been around for a long time and is still used. Why is it not included? Lehasa (talk) 19:06, 17 January 2009 (UTC)
A table is definitely needed about the clustering capabilities of relational databases. For instance middleware, Master-Slave. Sync Multimaster, etc. Specially I don't have too much info about Sync Multimaster. So far I only know about Oracle and Microsoft SQL capable of that. I beleive MySQL doesn't have plan to include that and that Postgres is working on it but then I'm not sure. PLease clarify. —Preceding unsigned comment added by 201.220.215.11 (talk) 07:55, 21 September 2008 (UTC)
This page definitely needs an overview of which transaction types the databases support. For many applications, it is important that you can start a transaction, make 100 select queries over a period of 10 minutes, and know that the first and last query will deliver the same result if they're identical, even if the database is being used and written to by other users in the same time period. It's needed because that's the only way you can make correct multi-query reports from production databases. For instance, Microsoft SQL Server 2000 doesn't support this. Also, it would be interesting to know what the default transaction type is - because that's typically the one that people use.87.63.152.70 (talk) 06:48, 1 May 2008 (UTC)
So Postgres doesn't have materialized views but gets away with a "it can be done with triggers"? In that case, the same should go for MySQL. Just do a search on "materialized views mysql" and you will get similiar solutions that use stored procedures and triggers. The implementation referred to in the footnote doesn't utilize any functionality specific to Postgres. --Juha001 11:26, 7 April 2006 (UTC)
Why are Microsoft SQL Server's indexed views only "similar" to a materialized view? -- A.M. 14 April 2006
ease in reordering columns? Jaydlewis (talk) 04:50, 26 December 2008 (UTC)
Would this be the right place to compare SQL compatibility with each database? Or is there another article that does this? For example, Interbase does not seem to support the MINUS operator (part of SQL). I was hoping to find a table listing tidbits like these. The management guys might also like a comparison of how "SQL-compliant" a database is, when it comes time to consider one. // Brick Thrower 15:00, 25 January 2007 (UTC)
I can see the argument that an empty entry in a comparison table encourages people to fill them in, but it leaves the current state of the article appearing amateurish and silly. If so little is known about an entry as to make it useless for the purpose of comparison lets exclude it entirely, rather than insert a bunch of kludgy "?" reminding us of what we do not know. We can use the discussion area for notes until enough is known to make the addition useful. *Note* I have not taken the action of reverting anything. EvanCarroll 15:52, 26 July 2007 (UTC)
A couple of other pieces of basic information about these databases would be useful.
A number of them, like Derby, are in-memory RDBMSes. This ought to be at least noted if not added as column of information. I'm not sure if there is some more general categorization of the RDBMS that this could be part of.
Nevermind the messy issue of SQL compatibility, but whether the interface to the RDBMS is SQL at all as opposed to something else should be noted. I believe Adabas is a non-SQL RDBMS, though there are SQL "gateways" that will translate SQL into a native Adabas query. There are also RDBMSes being developed (such as Rel and Muldis Rosetta) based on Date and Darwins 3rd Manifesto, which use implementations of Tutorial D instead of SQL. I think a column should be added title "Interface" or something similar, under which should be SQL for most RDBMSes, but may be other things. --Ericjs 17:06, 31 October 2007 (UTC)
The last two columns of the available indexes table, GiST and GIN are specific to just the one database. I'm sure that all databases have some such unique index schemes. I don't think that they really belong in this article. I propose removing these two columns. TallMagic (talk) 19:56, 1 May 2008 (UTC)
I'd like an admin to look into how this content was deleted. old revision I wrote that in 07' and it is still true today. How will anyone know what you mean when you say schema or database if the difference can be totally confused by a bad implementation. That is fairly unbiased and agreeably worded. I've added the content again, anew. If you have a problem with it bring it up onto the discussion page. EvanCarroll (talk) 04:11, 26 November 2008 (UTC)
eg pgAdmin vs SQL Server Enterprise Manager... Jaydlewis (talk) 04:55, 26 December 2008 (UTC)
I think 'Access control' section need to be renamed as 'Security'. It is more adapted as we don't speak only of access control but also confidentialy/encryption, security certification, ...
It would be nice to add some performance information here. Does anyone know about benchmarking tools for DMSs? Is there a reasonable way of comparesion at all? —Preceding unsigned comment added by 92.229.125.242 (talk) 16:51, 9 March 2009 (UTC)
I'm going to add a column "MAX column name length". I do believe this information will be useful for people who is porting one database to another. For example from MS Sql Server to Firebird or Oracle.
I googled and found the following sources:
http://www.mssqlcity.com/Articles/Compare/oracle_vs_db2.htm http://tracker.firebirdsql.org/browse/CORE-749 http://www.mssqlcity.com/Articles/Compare/sql_server_vs_oracle.htm http://dev.mysql.com/doc/refman/5.0/en/identifiers.html http://www.mssqlcity.com/Articles/Compare/sql_server_vs_oracle.htm http://forums.devshed.com/postgresql-help-21/max-table-name-column-name-size-600049.html
I know some might not confirm to the wikipedia standard for sources, but at least its a start.
Regards,
It could be interesting to add information regarding support for Concurrent Data Readers, that is the ability to "for a concurrent data reader to access more than one result set in the same database connection and query both of those result sets concurrently" AFAIK only DB2 (http://www.databasejournal.com/features/db2/article.php/3565831) and MS SQLServer (using M.A.R.S) support it (but I guess Oracle also supports it). I have searched of any indication that opensource databases support such feature (PostgreSQL, MySQL, H2, etc) but have been unable to find any page that confirms support.
I do not to which of the already existing table should the "Concurrent Data Readers" column should be added (or perphas a new comparision table with "Connection Capabilities" should be created? —Preceding unsigned comment added by 201.155.6.245 (talk) 14:36, 6 July 2009 (UTC)
41.247.1.82 (talk) 18:32, 28 May 2009 (UTC)
The column "Max table size" says "4 GB * block size (with BIGFILE tablespace)" without any explanation or footnote. This isn't easy to understand and perhaps "4 GB" is misleading or even wrong?
The article Super-Sizing A Database: Oracle 10g Tablespace Enhancements by Jim Czuprynski 28th October 2005 explains this much better in the section "Size Does Matter: BIGFILE Tablespaces": "A BIGFILE tablespace's datafile can now hold up to 4,294,967,296 (yes, you read that correctly - the multiplier is over 4 billion) blocks of data storage space. This means that a tablespace could conceivably hold up to 128 TB of data if the maximum Oracle tablespace block size of 32K is used."
In other words an Oracle table can be: 4,294,967,296 * 32 kB = 128 TB.
--Ohedland (talk) 11:43, 19 August 2009 (UTC)
The assertion that the maximum row size in Oracle is 8KB is also incorrect. While it does not appear in a document, at least as of version 10.2 of Oracle, the row size can easily exceed 8KB. For example, this is perfectly valid:
CREATE TABLE BLEAH (
A1 CHAR(2000 BYTE),
A2 CHAR(2000 BYTE),
A3 CHAR(2000 BYTE),
A4 CHAR(2000 BYTE),
A5 CHAR(2000 BYTE),
A6 CHAR(2000 BYTE),
A7 CHAR(2000 BYTE));
This example can be extended to the full 1000 column limit to create a table with a physical row length of 2000000 bytes. So, while the row length limit is not apparently documented, it is definitely not 8K.
--12.106.238.251 (talk) 15:30, 16 June 2010 (UTC)
MyISAM does not have a table storage limit of 256TB! The default pointer sized used by version 5+ is 6 bytes, so this is true *by default*. However all versions support up to 8 byte (64bit) pointers, and hence 2^64 bytes = 16 Exabytes is permitted. You can control this when creating your table or when altering it, by setting: MAX_ROWS and AVG_ROW_LENGTH. —Preceding unsigned comment added by 118.209.3.231 (talk) 06:10, 18 December 2009 (UTC)
Been using the beastie for 8 years in decision support role. works OK - http://www.dbmaker.com.tw/ was their link IIRC. 212.188.108.126 (talk) 19:02, 4 September 2009 (UTC)
Please add price of each RDMS. Thank you! —Preceding unsigned comment added by Meocon quyet doan (talk • contribs) 03:25, 19 January 2010 (UTC)
To adhere to Wikipedia policy, this comparison needs to include entries that have an article, and not include lists of external links. See for example Wikipedia:WTAF and Wikipedia:External links. Greenman (talk) 12:34, 4 February 2010 (UTC)
FEATURE TABLE USE OF NON-STD FOOTNOTES The Features table uses a confusing combination of standard (Wikipedia) footnotes and non-standard notes. I was going to add a web reference to the SQLite API, but edit PREVIEW the Wikipedia assigned footnote number was NOT the "NOTE" number at the bottom of the table. BTW, the reference to the SQLite API is: http://sqlite.org/cintro.html It wasn't strictly necessary for understanding to footnote the SQLite API (except to prevent it from being deleted), however the footnote glitch prevented me from listing GUI's that are specifically designed to work with SQLite, but that are only available at URLs other than sqlite.org. GUIs for SQLite links: http://www.sqlite.org/cvstrac/wiki?p=ManagementTools
Jim.Callahan,Orlando (talk) 15:59, 19 September 2013 (UTC)
Can someone show what 'Shadow' partitioning is? It is a heading in the Partitioning table, but only Firebird and InterBase support it. Since these have a common origin, this would seem to be a platform-specific term. 'Shadow partitioning' is not mentioned in the Partitioning article, and I have not come across it in any RDBMS platform I have used. I suggest deleting this column. 80.194.100.111 (talk) 16:17, 21 September 2010 (UTC)
Why is AmigaOS (and possibly also Symbian) included on the operating system compatibility table? This should only really contain mainstream (server) operating systems. Perhaps changing Unix to AIX and Solaris would also be useful. — M3TA(info) @ 19:49, 20 March 2011 (UTC)
How can a non-relational DBMS be on a list of Relation DBMS's? Sounds quite weak to me, should be removed from this list just as all other DBMS's that do not support referential integrity which is the key to being relational. —Preceding unsigned comment added by 82.169.68.36 (talk) 00:24, 11 March 2010 (UTC)
Some RDBMS, e.g. MySQL/MariaDB, have DB engines which maintain referential integrity, and some which don't. Claiming that they offer 'partial' support is misleading. They give you the choice of ACID conformance, when you need it, as well as offering options that don't incur the overhead. Open source is all about choice... — Preceding unsigned comment added by 75.73.1.89 (talk) 15:32, 4 October 2014 (UTC)
The various tables don't document "free to use" versions of various proprietary products clearly.
For example:
Microsoft SQL Server Express (free to use, technical limitations) Oracle Personal Edition (ditto)
There are a number of others, I'm sure (DB2? Sybase? Informix?)
Also, lower cost cut down versions and embedded versions not well addressed
For example Oracle Standard One (cut down from Enterprise--may be best handled by a footnote) Oracle Lite (embedded, not code related) Oracle Times10 (in memory) Sleepycat (also now owned by Oracle, I think it qualifies as relational)
188.222.243.54 (talk) 17:39, 19 May 2010 (UTC)MilesT
section is 100% original research - marked as such Kaelfischer (talk) 22:38, 10 June 2010 (UTC)
Many people coming to the page are only interested in comparing current RDs to decide which to use. However, because all of the comparison tables are multiple screens long and compare every RD that has ever existed, they find the page to be mostly useless. We need a way to show only current information for those who want it, in order to increase utility. A method for allowing the viewer to sort information and suppress what they don't need would also be good.
This is a general comment applicable to all comparison articles. —Preceding unsigned comment added by 136.142.206.28 (talk) 22:45, 15 October 2010 (UTC)
It may be interesting to also have a Max Index Length column in the Limits comparison but I do not have access to every database and this data is not quite documented in every database.
Would anyone also like to see it? Would you help me gather that information?
Here are the limits for MySQL InnoDB http://dev.mysql.com/doc/refman/5.5/en/innodb-restrictions.html#id922640 —Preceding unsigned comment added by 195.235.227.10 (talk) 12:34, 1 April 2011 (UTC)
Some databases have very basic ALTER TABLE support
http://www.sqlite.org/faq.html#q11
http://stackoverflow.com/questions/2385020/how-to-alter-a-column-datatype-for-derby-database
What section should include ALTER TABLE support? — Preceding unsigned comment added by 2.137.153.245 (talk) 17:49, 26 August 2011 (UTC)
I do not know what you mean by that.
Please add at least a reference or I will remove it. — Preceding unsigned comment added by 195.235.227.10 (talk) 12:59, 21 September 2011 (UTC)
It seems like Oracle Database has proper fine grained locking while Microsoft SQL Server does not. http://stackoverflow.com/questions/1437200/sqlserver-2005-deadlock-problem-with-no-shared-records
Would someone help me filling what databases have proper fine grained locking? — Preceding unsigned comment added by 193.127.207.152 (talk) 10:12, 5 October 2011 (UTC)
Someone added MariaDB again to the comparison but being just a fork has (right now) exactly the same features. http://kb.askmonty.org/en/mariadb-versus-mysql
Should we keep forks in the comparison that have the same features? — Preceding unsigned comment added by 193.127.207.152 (talk) 10:35, 5 October 2011 (UTC)
I think that it this article would be a lot more useful if it would also categorize database management systems by whether they use a client/server model or are serverless, or any other kinds of IPC (Inter-Process Communication) that they use. For example this makes a big difference between MySQL and SQLite. I added the stub category "Category:Database management systems by process model". I also requested an article for "List of serverless database management systems". It would be helpful to programmers and readers to have a list of serverless database management systems here in the comparison groupings and/or in a separate article, and the DBMS's should be categorized as such.
Some databases like Apache Derby do not support Multiversion concurrency control[1]
Should we add this feature to the comparison? Where should it be added? — Preceding unsigned comment added by 85.53.50.115 (talk) 12:28, 25 May 2012 (UTC)
Is Base considered a relational database?, if so it could be added to comparision Jonpatterns (talk) 10:43, 12 May 2013 (UTC)
As a currently-popular choice, I wish that this article covered the MySQL fork "Percona Server".
Doctorgage (talk) 00:07, 19 September 2013 (UTC)
If unmaintained but not SaaS, I guess not (disagree?). However for Saas as Xeround Cloud Database that planned to shut down by now even for paying customers I guess (if really gone). comp.arch (talk) 15:13, 26 February 2014 (UTC)
"Postgres lacks off-the-shelf cross-database functionality that MySQL has". Now that PostgreSQL has foreign-data-wrappers, I'm not sure this is true, but I'm not familiar with all the issues there. comp.arch (talk) 13:52, 14 April 2014 (UTC)
This edit request by an editor with a conflict of interest has now been answered. |
Hello, I have a conflict of interest for this article because I am being paid by NuoDB to help them add information. We would like to add NuoDB’s data to the following sections: Operating system support, Fundamental features, Limits, Tables and view, Indices, Database capabilities, Data types, Other objects, Partitioning, and Access control. I understand that I am not supposed to edit articles where I have a COI, so I’m asking for someone to do it for me. I have all the data and can provide it to any editor willing to add it for me. Bcooper87 (talk) 13:56, 28 May 2015 (UTC)
This help request has been answered. If you need more help, you can , contact the responding user(s) directly on their user talk page, or consider visiting the Teahouse. |
Hi! I am wondering if someone can help me with this request. Thank you!Bcooper87 (talk) 16:10, 23 July 2015 (UTC)
It doesn't provide ANSI SERIALIZABLE isolation level (allows non-serializable executions). So, it lacks full transaction isolation. Or, if ACID actually means nothing these days, why not just remove its line? This is the citation from this wiki (https://en.wikipedia.org/wiki/Snapshot_isolation): "Snapshot isolation is called "serializable" mode in Oracle..." 176.194.72.92 (talk) 01:26, 18 October 2015 (UTC) anonymous
Hello fellow Wikipedians,
I have just added archive links to one external link on Comparison of relational database management systems. Please take a moment to review my edit. If necessary, add ((cbignore))
after the link to keep me from modifying it. Alternatively, you can add ((nobots|deny=InternetArchiveBot))
to keep me off the page altogether. I made the following changes:
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ((Sourcecheck))
).
An editor has determined that the edit contains an error somewhere. Please follow the instructions below and mark the |checked=
to true
Cheers.—cyberbot IITalk to my owner:Online 02:02, 29 February 2016 (UTC)
In the table referential integrity for MySQL is yes and for MariaDB is partial. However, they both have the same limited 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." Perhaps this is a mistake and they are both partial? Jonpatterns (talk) 13:16, 16 April 2016 (UTC)
Max Row size on Limits table would be better is values are listed in kb as the lowest unit - to make comparison easier. Jonpatterns (talk) 13:16, 16 April 2016 (UTC)
SAP HANA information is completely missing. I added some information. Does anyone know more details about HANA? Feel free to add more details if you have any information. — Preceding unsigned comment added by Stvw80 (talk • contribs) 05:11, 17 June 2016 (UTC)
I can't locate MongoDB in here - but it's quite popular.--185.67.228.2 (talk) 15:03, 12 April 2017 (UTC)
Hello fellow Wikipedians,
I have just modified one external link on Comparison of relational database management systems. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
((dead link))
tag to http://sybooks.sybase.com/onlinebooks/group-as/asg1250e/sag/%40Generic__BookTextView/3225%3BWhen you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template ((source check))
(last update: 5 June 2024).
Cheers.—InternetArchiveBot (Report bug) 17:42, 11 August 2017 (UTC)
Why is Filemaker listed under all the tables except for fundamental features? I checked going back to 2011 and it has apparently never been listed. I don't know it myself (it's why I came to the article), but someone ought to fill it in. KarlM (talk) 07:26, 7 March 2018 (UTC)
This table makes me a bit confused as it seems to combine pure SQL syntax/functionality and optimization techniques. Or am I completely wrong here? AFAIK the MERGE JOIN is nothing but a dbms optimization trick to perform better, or does it have its own SQL syntax and a different result (different than regular JOIN)?
And doesn't parallel queries fall into the same category?
I'd prefer two separate tables, one for pure SQL functionality (INNER/OUTER JOIN, UNION, INTERSECT etc.), and another table for underlaying dbms performance functionality. — Preceding unsigned comment added by 94.234.39.197 (talk) 09:41, 31 July 2020 (UTC)
Can someone eXplain the choice of background color in the license column? I find it quite irritating to see proprietary licenses, GPL, and public domain use the same shade of purple. What does it mean? --2A02:8109:9AC0:1E40:AC4B:F238:F73:D435 (talk) 12:09, 1 April 2021 (UTC)