The Forum has been Updated
The code has been upgraded to the latest .NET core version. Please check instructions in the Community Announcements about migrating your account.
MySQL 5.0 is the most ambitious release in MySQL's history. MySQL 5.0 delivers the enterprise features the community has been asking for, including Stored Procedures, Triggers, Views, Information Schema, XA Distributed Transactions, and new Storage Engines. We also added Strict SQL Mode to eliminate some of the ‘Gotchas’. Plus, MySQL 5.0 builds on our reputation for Reliability, Performance, and Ease of Use.
More information and how to use the new features found at the MySQL developers site:
http://dev.mysql.com/
Download mirrors found here: http://dev.mysql.com/downloads/mysql/5.0.html<
More information and how to use the new features found at the MySQL developers site:
http://dev.mysql.com/
Download mirrors found here: http://dev.mysql.com/downloads/mysql/5.0.html<
Posted
Interesting before SQL Server 2005 :) Will see what's up with those two :)<
Posted
Posted
Originally posted by SiSLThere is no possible comparison between them.
Interesting before SQL Server 2005 :) Will see what's up with those two :)
As the post says, they are now offering entreprise features, that have been available in SQL Server for quite some time. The new features in SQL Server 2005 have nothing to do with this...<
Posted
But which one would you rather use ? 
<
<
Posted
That really depends on the purpose.
I spent the whole saturday moving a database from MSDE to MySQL. Several problems occurred, including problems with character conversions. Moving this from Access to SQL Server is a problem free operation, with MySQL, even with the tools provided by the MySQL developers, is a much troublesome experience, IMVHO, and I'm not only considering this experience.
It's quite common for export / import tools to fail without so much as warning, for example, specially when you use extended insert syntax. If you need a DB to support transactions, you need to use the InnoDB engine. Most servers are not optimized for InnoDB tables so that usually results in worse performance... and I could go on.
So, given the choice, I'd always go with SQL Server. If you plan to deal with XML in your database, use extended data types, have extensive use of user defined functions and stored procs, plan to use user defined types or user defined aggregate funtions, use the database to persist objects from an OO app, SQL Server would be the preferred DB (this a brief list of new SQL Server 2005 features).
Even with the enterprise features of MySQL, you should remember that those are new features for MySQL, but they have existed for quite a while in SQL Server...
Biggest MySQL advantage: price. I haven't been able to test SQL Server 2005 performance, but I would expect it to improve over the current version...
All in all, IMO, SQL Server is a more robust, better performing app, specially for an enterprise. For Snitz use, MySQL can be a good low (no) price option. Personally I only go with MySQL when SQL Server is not available, or not available at a reasonable price.
<
I spent the whole saturday moving a database from MSDE to MySQL. Several problems occurred, including problems with character conversions. Moving this from Access to SQL Server is a problem free operation, with MySQL, even with the tools provided by the MySQL developers, is a much troublesome experience, IMVHO, and I'm not only considering this experience.
It's quite common for export / import tools to fail without so much as warning, for example, specially when you use extended insert syntax. If you need a DB to support transactions, you need to use the InnoDB engine. Most servers are not optimized for InnoDB tables so that usually results in worse performance... and I could go on.
So, given the choice, I'd always go with SQL Server. If you plan to deal with XML in your database, use extended data types, have extensive use of user defined functions and stored procs, plan to use user defined types or user defined aggregate funtions, use the database to persist objects from an OO app, SQL Server would be the preferred DB (this a brief list of new SQL Server 2005 features).
Even with the enterprise features of MySQL, you should remember that those are new features for MySQL, but they have existed for quite a while in SQL Server...
Biggest MySQL advantage: price. I haven't been able to test SQL Server 2005 performance, but I would expect it to improve over the current version...
All in all, IMO, SQL Server is a more robust, better performing app, specially for an enterprise. For Snitz use, MySQL can be a good low (no) price option. Personally I only go with MySQL when SQL Server is not available, or not available at a reasonable price.
<