> The staff on the other hand, is thinking in using
> ORACLE, and I need very solid arguments to beet them. Any ideas I can
borrow?
There is really only two arguments against Oracle as a DBMS - price and
closed source. But then you have to ask what the argument is against MySQL.
When I started choosing my own DBMS, I needed replication and reliable
support, which excluded PosgreSQL. I therefore took the view that the
choice was MySQL until I found a reason otherwise. Two years on, I have yet
to find that reason.
As well as a DBMS, as I understand it Oracle provides a lot of tools
layered on top of the basic SQL DBMS. If you need these, then your choice
is made. But in many cases, it seems to me that the preference for Oracle
is past experience and/or FUD. Which makes it a very expensive security
blanket.
I find the open source aspect of MySQL very reassuring. I have has
experience in the past of closed source packages where I *know* there is a
bug in there, but I cannot do anything about it. I have not yet had to do
so, but I find it immensely reassuring that, if I need to, I can look at
the inner workings of MySQL.
I have had very positive results indeed from the MySQL support contract,
and would recommend it to anyone making serious professional use of MySQL.
By contrast, another department in this company which uses Oracle has
stopped buying support from Oracle because they did not consider it good
value for money. They now have a policy that new applications will prefer
MySQL to Oracle if they do not interact with existing Oracle applications.
Alec
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
