什么时候选择Oracle over MySQL？ [英] When to choose Oracle over MySQL?

问题描述

我是一个MySQL粉丝，但是我想知道在哪些情况下选择Oracle over MySQL看起来像去的方式..像什么将指示器，这会让你说我需要Oracle这个项目

I am a MySQL fan , however i want to know in which situations choosing Oracle over MySQL seems like the way to go .. like what would be the indicators which would make you say .. "I need Oracle for this project"

更新：
另一位同学SOer指出，不要限制您对Oracle的回答...如果你知道更好的东西，请指出。

Update: As another fellow SOer pointed out, dont limit your answers to Oracle ... if you know of something better , please point that out too.

推荐答案

有一些事情让我困扰我Mysql

There are certain things that bother me with Mysql

必须在强制执行约束和交易之间进行选择 - 全文索引（InnoDb vs MyISAM）。这真的是我的问题编号1（强制执行约束和交易是什么使得dbs酷，但你需要全文搜索...）

I have to choose between enforcing contraints and transactions vs Fulltext Index (InnoDb vs MyISAM). This is really the problem number 1 for me (enforcing contraints and transactions is what makes dbs cool, but you need the fulltext search too...)

• 在客户端代码中模拟事务并不容易。


• 如果不强制实施约束，那么很容易得到db的不一致状态


• 如果没有全文搜索，您可能会对OR X LIKE％y％感到疯狂


• 您必须使用RAISE ERROR创建BEFORE UPDATE TRIGGER才能执行CHECK CONSTRAINT


• 当数据变得太大（我的意思是真的很大）时，Mysql的性能很差。


• Mysql创建不良的执行计划


• Mysql在超过3个连接时遇到问题（更好地说多个连接）。

• It is not easy to "simulate" transactions in client code.
• If you don't enforce the constraints it is really easy to get inconsistent state of the db
• Without Fulltext Search you might get crazy with OR X LIKE %y%
• You have to create BEFORE UPDATE TRIGGER with RAISE ERROR for CHECK CONSTRAINT
• Mysql has bad performace when data becomes too large(I mean really large).
• Mysql creates poor execution plans
• Mysql has problems with more than 3 joins(let's better say multiple joins).

Oracle是所有这些问题的解决方案，它是一个完整的DBMS（事务，CHECK约束，许多视图选项，全文搜索等等） ），但毕竟它是一个钱的问题。

Oracle is the solution for all these problems, it is a full DBMS (transactions, CHECK contraints, a lot of options for views, fulltext search and much more.. ) but after all it is a matter of money.

这篇关于什么时候选择Oracle over MySQL？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！