John Sheppard wrote:
> Hello,
>
> I am evaluating mySQL as an alternative to SQL Server...Other guy wants
> to go SQL Server, I kinda like mySQL...
>
> What steps can be taken for mySQL so that I can be guaranteed to be ;
> a) ideally corruption free
> b) 100% safe if corruption does occur
>
> Can anyone recommend any transaction logging tools, hot backup tools.
> Should I be worried about mySQL's atomicity? Im still fairly new to
> databases...I come from msaccess background...
>
> I have read a fair bit on it but most information I find is dated pre
> 2004, I see less people bagging out mySQL after that date....but still a
> few things concern me...things i cant articulate at this moment
>
> Thank you
> John Sheppard

given the choice of MySQL, SQLServer or Oracle Express(10g)for ANYTHING
production where I bet my business on the data, I would rank them OE,
SQLServer, MySQL. MySQL is good, but as a long time Database
consultant, would not bet my bottom line on it. It can be a good
"front-end" database where you upload data to a real database engine
frequently. OE and MySQL run on something other than Windows - like
Linux, which only slightly more secure.

Bottom line would be the use - and only you can decide whether or not to
chance losing your data. We all have our preferences, but it comes down
to risk - usually $$$$. SQLServer ain't cheap. PostgreSQL is also a
good alternative.

I have never been a fan of the methods used for backing up MySQL. On my
OpenVMS server, I shut down the database and backup all the data
files. I actually restored just the data files from one server on
another and restarted the database(s) without a single hiccup. My
system backup tool does an "image" backup of the database and since
MySQL is down at the time, and I have no doubt about recovery.