Re: [cobalt-users] MySQL limits- OFF TOPIC -

["Frederic Stos" <metalwolf@xxxxxxxxxxxxx>]

> > When is it a good time to consider migrating to a more efficient
> db -
> > Oracle maybe?
> 
> That really depends. Oracle is not more efficient than MySQL in
> *everything*; last time I checked the MySQL site, they were claiming
> that MySQL whipped Oracle's butt on quite a number of issues.
> Personally I'd say you'd have to have one huge amount of data and/or
> users - and I really mean HUGE - before you'd need to leave MySQL, if
> at all.

Gee.. I am not really agree with you on this point Carrie.
Mysql as many many integrity problems and holes...
As inexistant foreign keys, no transactions (you know... commit and rollback)
no efficient or none pre/post code , no integrated language (PS/SQL or Java 
as in ORACLE) which make a huge problem not even when data grows, but 
before... consider data importance and integrity... 
I explain myself:
Consider a electronic transaction. Maybe 6 or seven step between 
aceptation of user and payment done....
IF communications hang during transaction, you just CORRUPT your 
database 
(no the base itself, but HUGE LOSS OF INTEGRITY PROBLEMS !!!!)
And the work to do to program procedures on a mysql to prohibit this kind of  
problems is a large amount of time and debug and test, when on an oracle 
database is just a line more in any script.... (transactions and foreign 
keys......)

Oh and BTW, MySQL tends to corrupt regularly also, when a daemon crash, 
disk interrupt etc (always have a HOURLY backup at least......) ORACLE 
DONT and have redo log to recuperate exact database state before crashing 
, if ever exists.

I definitively recommend and ORACLE database on any sensible data 
where integrity cant be loss at any price 
(ie. talking about monney, sensible data for a company, even a portal or an 
intra/extranet)

I.E. Don't swap because huge amount of data... swap because of 
SENSIBILITY and IMPORTANCE of data

Other very interesting point: for using ORACLE:
Consider java integration
Consider Text indexing (Oracle knows any INSO text compatibility, you can 
index a excel or word document directly into the database, between more 
that 200 differents formats)
Consider XML integration : oracle already is 100% compatible with XML 
format (with posibility to store XML data hierarchically into the database), 
ORACLE is OBJECT ORIENTED,
Consider many other possibilities that Oracle offers you... check the 
ORACLE site.

Effectively, Oracle is expensive !
(over 250 USD each user licence for a workgroup....and 2000 USD for a 
universal server user licence....)

PS: I dont work for oracle hehehehehehhehe
I use myself 90% mysql for all my datas..... because of cost of course..


> 
> > What db's must be considered for the long term? - pref. working on
> linux -
> 
> I think you've got it nailed down - MySQL and Oracle. Stay away from
> anything Microsoft; but again I think you only need to migrate to
> Oracle if it's a personal preference of yours OR once you start
> noticing signs that the database is too big and performance is
> suffering. With a carefully created database, though, it's quite
> likely that you'll never hit that point with MySQL.
> 

Agree.. Stay FAR away from microsoft, but also from informix
Informix has HUGE problems with dates (well sorry, YOU'll have huge 
problems programming dates better said, it's a true mess)
and informix doesnt even knows the upper, lower, initcap functions !!!!!!
(imagine searching a match into a title or text.... gee... you HAVE to by the 
text extension which is as costly as oracle context option, but doesnt even 
make 5% of context option of oracle...)

MasterPhil