How solid is mySQL on a win2003 server with ASP

Is it completely reliable?

[steve]

This follows on from my post about intermittent connection problems with Access.

I didn't want to change databases at the moment, but I can't find a reliable solution.

So if I do convert my databases to mySQL and use their ODBC drivers with ASP scripts on a win2003 box running IIS6. How reliable is it going to be?

Is anyone doing this, if so is it stable, are there any gotcha's to watch out for?

I will be grateful for any feedback.

[dataguy]

I'm running a site with about 100 million queries daily to a MySQL 4.13 database and it has been very reliable from the beginning. Make sure you have the latest versions of everything, especially MDAC.

I hate to develop using MySQL so I have been developing using SQL Server and Enterprise Manager and then moving it over to MySQL once I have the kinks out. It's a little awkward but it works for me...

[txbakers]

W2003 is incredibly stable. No problems to report.

[Bluesplinter]

then moving it over to MySQL

How do you do that? I've been thinking about doing the same thing, but didn't want to have to write a custom script to read a record from MS SQL then insert into MySQL one-by-one.

Or vis-versa, for that matter... I have alot of stuff in MySQL now that I wouldn't mind working with in MS SQL. If nothing else, I'd like to test compare them, but I don't know an easy way to sync them.

[steve]

Thank you everyone for the comments.

I've switched to mySQL, it was much easier than I anticipated, and so far appears totally reliable.