Author |
Topic |
Davio
Development Team Member
Jamaica
12217 Posts |
Posted - 24 October 2005 : 23:23:25
|
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< |
Support Snitz Forums
|
|
SiSL
Average Member
Turkey
671 Posts |
|
Shaggy
Support Moderator
Ireland
6780 Posts |
Posted - 25 October 2005 : 07:07:31
|
Funky, will have to check it out when I have a bit of time. Thanks, Davio
< |
Search is your friend “I was having a mildly paranoid day, mostly due to the fact that the mad priest lady from over the river had taken to nailing weasels to my front door again.” |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 25 October 2005 : 08:07:04
|
quote: Originally posted by SiSL
Interesting before SQL Server 2005 :) Will see what's up with those two :)
There is no possible comparison between them. 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...< |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
laser
Advanced Member
Australia
3859 Posts |
Posted - 25 October 2005 : 09:38:15
|
But which one would you rather use ? < |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 25 October 2005 : 10:18:45
|
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. < |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
AnonJr
Moderator
United States
5768 Posts |
Posted - 25 October 2005 : 11:09:11
|
Given that, how does the Express version (of SQL Server 2005) fit in?< |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 25 October 2005 : 11:42:41
|
Frankly I don't know the Express version. It has the limitations we discussed previously, but I guess it should have all the other major features. Can't be sure about it though.< |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
laser
Advanced Member
Australia
3859 Posts |
Posted - 25 October 2005 : 17:24:52
|
If you're talking corporate, I wouldn't go past Oracle. Not really Snitz-friendly, but IMHO walks all over MS. But I'm a tad biased, I worked there for over 5yrs, but was more focussed on the multi-dimensional side rather than the relational side.< |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
Podge
Support Moderator
Ireland
3775 Posts |
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
AnonJr
Moderator
United States
5768 Posts |
Posted - 25 October 2005 : 18:28:59
|
quote: Originally posted by Podge
And if you thought you needed a degree to figure out Microsoft's licencing you need a PhD to figure out Oracles - http://www.oracle.com/corporate/pricing/eplext.pdf
Must ... find ... asprin ... < |
|
|
-gary
Development Team Member
406 Posts |
Posted - 25 October 2005 : 21:59:37
|
All I want is MS SQL to do a simple cluster and I'd be happy. Fault tolerance and automatic fail over are two things that MS hasn't even gotten close to yet. Not that MySQL's implemention is much better than a single point system, but at least it has some support for it.< |
KawiForums.com
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 25 October 2005 : 22:47:40
|
Seems like those features are improved in SQL Server 2005. You can have a look at the SQL Server site, there is a lot of info on high availability capabilities of the new SQL Server version.< |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
Topic |
|