MySQL is a decent product.  I've been very critical of it in the past, but it has been evolving nicely.  It's probably the most popular open source database and plays nicely with .NET due to a solid ADO.Net provider.  What's been lacking up to this point, though, is LINQ to SQL support, and more recently a provider for the Entity Framework.  The EF has gotten a lot of flak, but I for one like it for the most part and I think it will hugely speed up a lot of database-heavy development. Sure, you need to write some extension methods to get around the lack of foresight for how change-tracking would work in ASP.Net applications, but once you've cracked that nut (and grokking aggregates with Entity SQL)  you can go back to happily writing LINQ queries.

I have been watching the MySQL forums for a while. The MySQL team had said during the Beta of VS2008 SP1 that there would be something we could test "real soon".  This was followed by months of radio silence.  Recently, silence was finally broken by the lead developer that September 30th was the date.  MySQL subsequently set up a webcast to demonstrate the new functionality.  Today, the day of the webcast, it seems that registered participants got messages saying that November 4th was the new date.  Unbelievable.  See: http://forums.mysql.com/read.php?38,194470,228269#msg-228269

When I was in consulting, we had a tongue-in-cheek (yet very true) rule about deadlines.  If the deadline was to be pushed back, it could only be pushed back by the amount of time remaining until the delivery date.  If you have 3 weeks until the deadline, you can only move the deadline out 3 weeks.  If it's due tomorrow, you can only push it out one day.  You do not wait until it's due today and push it back a month.  I'm sure there's a reason, but it's just bad form.  People are on the edge of their seats over this feature.  This isn't how open source is supposed to work.