Murty wrote:
> We are thinking of migrating a mission critical application from
> Informix/Solaris to MySQL/Linux platform. It is a OLTP app and has
> got 400 gb of data with @ 800 tables, few stored procs and triggers.
> Lot of business logics is there in the form of 'C' Embedded SQL
> routines. Some of the big tables have been partitioned. Average # of
> DB users is @ 100.
> Can MySQL realistically handle this kind of app ?
> Does it have Embedded SQL pre-processor for C/C++ ?
> Any experiences/thoughts are greatly appreciated.
> Thanks
> Murty
>

Murty,

MySQL is pretty good - as stable as any of the databases out there. It
also is quite good at optimizing calls, although some are better.

MySQL doesn't have a preprocessor - everything is done with function
calls. This has advantages and disadvantages - it's easier to program
without the extra step, but if the database is maintained properly
(reorganized, etc. when necessary), preprocessed SQL typically runs faster.

It should do what you need quite well, and won't be much slower than any
of the others - chances are you won't even be able to tell the difference.

Of course, if you need even this slight improvement, you can go to one
of the more expensive databases. Personally, I'd recommend IBM's DB2 in
that case.

But I'd still recommend MySQL unless it has something you just can't do
without.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================