I wish they'd implement transactions correctly first. I was doing a "DELETE FROM" the other night and it wound up forcing a commit for no good reason. Uhh, 'kay! Luckily, I did have a backup. I've had enough fun MySQL adventures to know to do that before doing anything that would be a safe operation in another RDBMS.
I've been using MSSQL at my day job and it's like night and day. The language is closer to the actual T-SQL standard (MySQL tends to drift quite a bit away from it in a lot of ways), the tools are far better (SQL Management Studio isn't crash-happy like MySQL Workbench and isn't exceedingly slow in large queries like the Query Browser, and the SQL Server Profiler is pretty much the best thing EVER, letting you see what queries are running in real-time as they're happening -- far better than the MySQL Administrator), and it's far easier to set it up for optimal use.
I don't care how much enterprise usage MySQL gets. As far as I'm concerned, the only thing that's allowing it to get that much use is its price tag. Nothing can possible make up for some of its terrible flaws and the poor quality control on their related projects (the MySQL .NET Connector, for one, is one of the worst .NET components I've ever had the "pleasure" of working with).
