1. Redgate Sql Compare

Microsoft SQL Server vs. Oracle: The Same, But Different? Written by Josh Stansfield on March 13, 2014. Also, in SQL Server each database has a private, unshared disk file on the server. In Oracle, all the database objects are grouped by schemas, which are a subset collection of database objects and all the database objects are shared among.

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[edit]

Operating system support[edit]

The operating systems that the RDBMSes can run on.

Fundamental features[edit]

Information about what fundamental RDBMS features are implemented natively.

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): MySQL provides ACID compliance through the default InnoDB storage engine.^[55][56]

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

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

Redgate Sql Compare

Note (5): MySQL provides GUI interface through MySQL Workbench.

Note (6): MariaDB's default XtraDB engine is ACID compliant.

Note (7): OpenEdge SQL database engine uses Referential Integrity, OpenEdge ABL Database engine does not and is handled via database triggers.

Limits[edit]

Information about data size limits. Gujarati bhajan lyrics in english.

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

Note (2): Limit is 10³⁸ using DECIMAL datatype.^[62]

Note (3): InnoDB is limited to 8,000 bytes (excluding VARBINARY, VARCHAR, BLOB, or TEXT columns).^[63]

Note (4): InnoDB is limited to 1,017 columns.^[63]

Note (6): Using VARCHAR (MAX) in SQL 2005 and later.^[64]

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,^[65] 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 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[edit]

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

Note (1): Server provides tempdb, which can be used for public and private (for the session) temp tables.^[66]Adobe premiere pro transition downloads.

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

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

Note (5): Materialized views are now standard.

Indexes[edit]

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

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

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

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

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^[106] 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[edit]

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

Data types[edit]

Other objects[edit]

Information about what other objects are supported natively.

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[edit]

Information about what partitioning methods are supported natively.

Note (1): Since version 8.1 PostgreSQL provides partitioning support through check constraints.^[147]

Note (2): Raima Database Manager 14.0 requires the application programs to select the correct partition (using range, hash or composite techniques) when adding data, but the database union functionality allows all partitions to be read as a single database.^[148]

Access control[edit]

Information about access control functionalities (work in progress).

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

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

Note (9): Authentication methods.^[162]

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

Note (11): Authentication methods.^[163]

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

Databases vs schemas (terminology)[edit]

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 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 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 (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 recently added 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.^[165] 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[edit]

• Relational database management system (includes market share data)
• Object database - some of which have relational (SQL/ODBC) interfaces.

References[edit]

1. ^http://www.4d.com/products/lifecycle.html
2. ^'Apache Derby: Downloads'. Retrieved 2019-03-11.
3. ^Derby - ASF JIRA
4. ^CUBRID / Jira Issue tracker for CUBRID
5. ^Stevens, O. (Oct–Dec 2009). 'The History of Datacom/DB'. Annals of the History of Computing. IEEE. 31 (4): 87–91. doi:10.1109/MAHC.2009.108. ISSN1058-6180. Retrieved 2014-07-06.
6. ^'CA Datacom - CA Technologies'.
7. ^'Datacom Product Sheet'(PDF).
8. ^IPL, Firebird SQL
9. ^IDPL, Firebird SQL
10. ^Firebird RDBMS Issue Tracker
11. ^HyperSQL Database Engine (HSQLDB) / Bugs
12. ^h2database issues
13. ^Linter Techsupport
14. ^'MariaDB 10.3.15, MariaDB Connector/C 3.0.10, MariaDB Connector/Node.js 2.0.5 and MariaDB Connector/ODBC 3.1.1 Now Available'. mariadb.org. 2019-05-14.
15. ^'MariaDB licenses'.
16. ^MariaDB - JIRA
17. ^MaxDB - Problem Tracking
18. ^MonetDB Jul2015 released, CWI
19. ^MonetDB Bugzilla
20. ^mSQL, Products, AU: Hughes
21. ^'MySQL 8.0 Release Notes'. mysql.com. Retrieved 14 May 2019.
22. ^MySQL Bugs
23. ^Issues · openlink/virtuoso-opensource · GitHub
24. ^Colgan, Maria (23 July 2018). 'Oracle Database 18c is now available for Download!'. Retrieved 3 December 2018.
25. ^Oracle Rdb Product Family Compatibility Matrix, Oracle Corporation
26. ^https://www.percona.com/doc/percona-server/LATEST/release-notes/
27. ^Polyhedra® Lite In-Memory Relational Database System Freeware Available Now from Enea, Press Release, EECatalog.
28. ^'PostgreSQL 11.3, 10.8, 9.6.13, 9.5.17, and 9.4.22 Released!'. PostgreSQL. The PostgreSQL Global Development Group. 2019-05-09. Retrieved 2019-05-09.
29. ^License, PostgreSQL Community
30. ^A bug tracker for PostgreSQL?
31. ^SQLite Release History, SQLite
32. ^SQLite: Ticket Main Menu
33. ^SQream DB Version 2.1 SQL Reference Guide, SQream Technologies
34. ^https://www.firebirdsql.org/en/firebird-3-0/
35. ^http://docs.actian.com/ingres/11.0/index.html#page/Ing_Install%2FB._Installing_Ingres_on_OpenVMS.htm%23ww245951
36. ^'Building MariaDB on Mac OS X using Homebrew'. AskMonty KnowledgeBase. Retrieved September 30, 2011.
37. ^https://play.google.com/store/apps/details?id=com.esminis.server.mariadb&hl=de MariaDB Android Version by Tautvydas Andrikys
38. ^http://blogs.microsoft.com/blog/2016/03/07/announcing-sql-server-on-linux
39. ^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
40. ^http://aminet.net/package/dev/gg/postgresql632-mos-bin
41. ^http://www.oss4zos.org/mediawiki/index.php?title=PostgreSQL#z.2FOS
42. ^Derby Developer's Guide (10.14)>Lock granularity
43. ^DB2 for Linux UNIX and Windows 9.7.0>Fundamentos de DB2>Performance tuning>Factors affecting performance>Application design>Concurrency issues>Isolation levels
44. ^http://www.h2database.com/html/advanced.html#mvcc
45. ^ ^abcTransactional DDL in PostgreSQL: A Competitive Analysis
46. ^Transactional DDL in MariaDB
47. ^SQL Server Transaction Locking and Row Versioning Guide
48. ^MySQL :: MySQL 5.6 Reference Manual :: 8.10.1 Internal Locking Methods
49. ^Oracle Row Lock and Row Level Locking
50. ^[developer.polyhedra.com/history/polyhedra-8-7 Polyhedra 8.7 new headline feature: locking]
51. ^PostgreSQL: Documentation: devel: Explicit Locking
52. ^BUG #5974: UNION construct type cast gives poor error message
53. ^File Locking And Concurrency In SQLite Version 3
54. ^SQLite Full Unicode support is optional and not installed by default in most systems (like Android, Debian…)
55. ^'MySQL - The InnoDB Storage Engine'.
56. ^'InnoDB - Oracle Wiki'.
57. ^'MySQL 5.6 Reference Manual'.
58. ^'Identifier Names'. MariaDB KnowledgeBase. Retrieved 26 September 2014.
59. ^http://grokbase.com/t/postgresql/pgsql-general/12bsww982c/large-insert-leads-to-invalid-memory-alloc
60. ^https://www.postgresql.org/docs/9.3/static/lo-intro.html
61. ^Technical Specifications, Guide, Firebird SQL
62. ^Library, MSDN, Microsoft
63. ^ ^ab'Column count limit', Reference Manual, MySQL Documentation (5.1), Oracle
64. ^'Row-Overflow Considerations', TechNet Library, SQL Server Documentation (2012), Microsoft
65. ^'Date functions', Language, SQLite
66. ^Online books, Sybase, archived from the original on 2005-10-23
67. ^Informix Performance Guide, Info Centre, IBM
68. ^Archives, Pure (13), Red Noize, archived from the original on 2006-04-23
69. ^'Derby', Full Text Indexing, Search, Issues, Apache
70. ^ ^abc'CUBRID 9.0 release'.
71. ^Full-text search with DB2 Text Search, Developer Works, IBM
72. ^Does Firebird support full-text search?, Firebird FAQ
73. ^Fulltext Search, Tutorial, H2 Database
74. ^Create Spatial Index, Grammar, H2 Database
75. ^Forest of Trees Index, Informix Infocenter, IBM
76. ^Full Text Search Functions(PDF), Documentation, RU: Linter
77. ^ ^abSPATIAL INDEX, MariaDB, mariadb.com, retrieved 24 September 2017
78. ^'Storage Engine Index Types'. mariadb.com. Retrieved 25 April 2016.
79. ^Virtual Columns - MariaDB Knowledge Base
80. ^'Fulltext Index Overview'. mariadb.com. Retrieved 25 April 2016.
81. ^Does Microsoft Access have Full Text Search?, Questions, Stack Overflow
82. ^'Microsoft SQL Server Full-Text Search', Library, MSDN, Microsoft
83. ^'Spatial Indexing Overview', Library, Tech Net, Microsoft
84. ^'Microsoft SQL Server Compact Full-text search is not available', Forums, MSDN, Microsoft
85. ^Index Types Per Storage Engine, MySQL, Oracle, retrieved 24 September 2017
86. ^'Feature request #4990: Functional Indexes', Bugs, MySQL, Oracle
87. ^'Feature request #13979: InnoDB engine doesn't support FULLTEXT', Bugs, MySQL, Oracle
88. ^'MySQL v5.6.4 Release Notes', Release Notes, MySQL, Oracle
89. ^Creating Spatial Indexes, MySQL, Oracle
90. ^Changes in MySQL 5.7.5, MySQL, Oracle
91. ^Does Oracle support full text search?, Questions, Stack Overflow
92. ^'Location Features for Database 11g', Spatial & Locator, Tech Network, Oracle
93. ^Oracle / PLSQL: ORA-01408 Error Message
94. ^Full Text Search, Documentation (8.4), PostgreSQL community
95. ^'4', Manual, PostGIS, PostGIS PSC
96. ^The SQLite R*Tree Module
97. ^SQLite Expression Indexes
98. ^SQLite FTS3 Extension
99. ^SpatiaLite (2.3.1), IT: Gaia GIS
100. ^Full-Text Search, Online Publications, Teradata
101. ^geospatial
102. ^UDF, Ad Hoc Data
103. ^'Create DB', Library, MSDN, Microsoft
104. ^'SQL', Library, MSDN, Microsoft
105. ^Petkovic, Dusan (2005). Microsoft SQL Server 2005: A Beginner's Guide. McGraw-Hill Professional. p. 300. ISBN978-0-07-226093-9.
106. ^'InnoDB adaptive Hash', Reference manual, Development documentation (5.0), Oracle
107. ^'Article', Library, Developer Works, IBM
108. ^ ^abcdefghttps://modern-sql.com/blog/2018-08/whats-new-in-mariadb-10.3#3.system-versioned-tables
109. ^ ^abNew Features in HyperSQL 2.2
110. ^H2 > Advanced > Recursive Queries
111. ^H2 Functions
112. ^Informix parallel data query (PDQ)
113. ^'INTERSECT'. mariadb.com.
114. ^'EXCEPT'. mariadb.com.
115. ^'CTE implemented in 10.2.2'. mariadb.org. Retrieved 26 July 2017.
116. ^'Window Functions Overview'. mariadb.com. Retrieved 25 April 2016.
117. ^ ^ab'Feature request #1542: Parallel query', Bugs, MySQL, Oracle
118. ^Only very limited functions available before SQL Server 2012, Microsoft
119. ^'SQL Server Parallel Query Processing', Library, MSDN, Microsoft
120. ^'Feature request #16244: SQL-99 Derived table WITH clause (CTE)', Bugs, MySQL, Oracle
121. ^Parallel Query, Wiki, Ora FAQ
122. ^Huber, Mathias (July 2, 2009). 'PostgreSQL 8.4 Proves Feature-Rich'. Linux Magazine. Retrieved 2016-10-17.
123. ^Parallel Query, PostgreSQL
124. ^SQLite Query Language: WITH clause
125. ^Window Functions
126. ^'Data Types', General Reference, HDB, Altibase
127. ^ ^ab'10. Data Types', Reference manual, MySQL (5.0), Oracle
128. ^'Data Types', CUBRID SQL Guide, Reference Manual, CUBRID
129. ^'FileMaker 14 Tech Specs'. FileMaker=May 12, 2015.
130. ^'Migration from MS-SQL to Firebird'. Firebird Project. Retrieved April 12, 2015.
131. ^'General: HSQLDB data types', Guide, Documents (2.0), HSQLDB
132. ^'IBM Informix Guide to SQL: Reference, v11.50 (SC23-7750-04)'. Publications. IBM. Retrieved August 7, 2013.
133. ^'3: Understanding SQL Data Types', SQL Reference Guide, Doucments (9.3), Ingres
134. ^'Data Types'. mariadb.com. Retrieved 25 April 2016.
135. ^'SQL Server Data Types', Library, MSDN, Microsoft
136. ^'SQL Server Compact Data Types', Library, MSDN, Microsoft
137. ^'Datatypes', SQL Reference, OpenLink Software
138. ^'Data Types', SQL Reference, Server documents (11.2), Oracle
139. ^'Data Types', Pervasive PSQL Supported Data Types, Product documentation, Pervasive
140. ^Polyhedra SQL Reference Manual, Product documentation, Enea AB
141. ^'Data Types', Manual, Documents (10), PostgreSQL community
142. ^'Defining a Database', SQL Reference (14.0), Raima
143. ^'Defining Table Columns', SQL Reference (8.3), Raima
144. ^Datatypes (3), SQLite
145. ^SQream SQL Reference Guide, SQream Technologies
146. ^'CONSTRAINT'. mariadb.com.
147. ^'Release', Documents, Developer (8.1), PostgreSQL community
148. ^'Database Unions', User's Guide (14.0), Raima
149. ^Support, Downloads, Sybase
150. ^'Release', Engine, Development (2.0), Firebird SQL
151. ^Files, Firebird SQL
152. ^'Trace and Audit Services'. Firebird Project. Retrieved April 12, 2015.
153. ^'cracklib_password_check'. mariadb.com. Retrieved 9 December 2014.
154. ^'simple_password_check'. mariadb.com. Retrieved 9 December 2014.
155. ^'Security Vulnerabilities Fixed in MariaDB'. mariadb.com. Retrieved 25 April 2016.
156. ^'Downloads', Development, MySQL, Oracle
157. ^Security, Support, PostgreSQL community
158. ^Audit trigger, Support, PostgreSQL community
159. ^Download, SQLite
160. ^DB, Products, Common Criteria Portal
161. ^Backup MySQL, How to, Gentoo wiki
162. ^Authentication methods, Documents (8.1), PostgreSQL community
163. ^Common Criteria (CC, ISO15408), Microsoft, archived from the original on 2014-02-13
164. ^Adding audit trails to a Polyhedra IMDB database, White paper, Enea AB
165. ^'PostgreSQL: Documentation: 9.5: IMPORT FOREIGN SCHEMA'. www.postgresql.org. Retrieved 2016-06-11.

External links[edit]

• Comparison of different SQL implementations against SQL standards. Includes Oracle, DB2, Microsoft SQL Server, MySQL and PostgreSQL. (8 June 2007)