I would get away from Windows for a very big reason ... OS CACHING !!!
The OS tends to take responsibility for caching disk caches and a server crash can easily lose data.
Even if all your data are InnoDB, the Windows version of MySQL does not support the option called innodb_flush_method called
O_DIRECT. Linux has mechanisms in place to dictate how and when to flush changes to data files. Those mechanisms do not exist in Windows according the MySQL Documentation on innodb_flush_method which says in the very first paragraph:
Controls the system calls used to flush data to the InnoDB data files and log files, which can influence I/O throughput. This variable is relevant only for Unix and Linux systems. On Windows systems, the flush method is always async_unbuffered and cannot be changed.
I wrote about the importance of innodb_flush_method : See my post Clarification on MySQL innodb_flush_method variable
Using Windows always leaves buffered data being flushed to disk solely at the discretion of Windows. You simply cannot take that risk, especially for a production database with heavy writes.
Please switch over to Linux ASAP.
MySQL being a better DBMS for Windows than SQL Server is open to much debate. I am sure SQL Server probably has been code to accommodate that Windows deficiency I just mentioned. I'll let the SQL Server big boys chime in on that issue.