There are any of numerous reasons that headquarters may have "forced" you to convert the project to SQL Server:

• Dynamic backups can be performed without taking the product off-line;
• SQL Server supports referential integrity checks, which MySQL can't do without InnoDB;
  
• SQL Server has supported stored procedures, allowing for n-tier design, while MySQL just recently began supporting them;
• True atomic transactions;
• SQL Server has a long history of enterprise acceptance and use, ranging from NASDAQ to Match.com,

among others.

I don't know what the project requirements are for your particular project, and I'm not saying that MySQL is a bad product. However, it is NOT a good foundation for an enterprise-level project. There are other "manly" databases available, such as PostgreSQL, Oracle 8/9/10, or db2, among others.

If you're running an updated version of Windows 2000 Server or Windows Server 2003, and SQL Server is crashing, then I'd suggest that you check your hardware to determine whether or not there's a physical problem that's causing your crashes.

Finally, you should look at what you, the programmer, are doing to introduce instability into your code base. Whatever it is, I wish you luck in finding the problem.

Ryan Cammer