Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Guest editorial: Reasons to be Cheerful Expand / Collapse
Author
Message
Posted Thursday, February 5, 2009 8:13 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 10:19 AM
Points: 1,951, Visits: 2,123
dphillips (2/4/2009)
One must understand that MySQL is a "plugin" architecture, where the SQL service engine is a layer over potentially many different types of engines (15+ types). This is a feature and a bug. Only one of these engines was advertised as ACID compliant (INNODB), and MySQL did not even own that engine.


To counter Oracle's purchase of INNODB, MySQL hired Jim Starke to help them develop the Falcon engine for MySQL 6. Alpha versions of this have had some performance issues though. I wonder how much effort was taken away from the 5.1 product line to help build 6.0? I can't imagine that's a 1 man job to create a new database engine plugin that's expected to be enterprise class.

While there may be some people who move from MySQL to SQL Server, I imagine people in that area would be more likely to move towards PostgreSQL, Firebird, or one of the other open source databases out there. Both of those are full featured databases that have ACID compliance, enterprise capabilities, and SQL Standards for years that MySQL has only recently gained. They also both run on many platforms, so if you're running MySQL on Linux, BSD, or Solaris, you're more likely to move to a different database that can run on the same hardware/OS you already have.
Post #650908
Posted Thursday, February 5, 2009 12:11 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, August 10, 2012 6:08 PM
Points: 1,156, Visits: 801
Chris Harshman (2/5/2009)
dphillips (2/4/2009)
One must understand that MySQL is a "plugin" architecture, where the SQL service engine is a layer over potentially many different types of engines (15+ types). This is a feature and a bug. Only one of these engines was advertised as ACID compliant (INNODB), and MySQL did not even own that engine.


To counter Oracle's purchase of INNODB, MySQL hired Jim Starke to help them develop the Falcon engine for MySQL 6. Alpha versions of this have had some performance issues though. I wonder how much effort was taken away from the 5.1 product line to help build 6.0? I can't imagine that's a 1 man job to create a new database engine plugin that's expected to be enterprise class.

While there may be some people who move from MySQL to SQL Server, I imagine people in that area would be more likely to move towards PostgreSQL, Firebird, or one of the other open source databases out there. Both of those are full featured databases that have ACID compliance, enterprise capabilities, and SQL Standards for years that MySQL has only recently gained. They also both run on many platforms, so if you're running MySQL on Linux, BSD, or Solaris, you're more likely to move to a different database that can run on the same hardware/OS you already have.


I completely agree with the first paragraph. I wonder about Sun's efforts to continue this?

On the second paragraph, it does put in perspective where MySQL really is in the pecking order. However, having used most of those other systems, I wouldn't call them enterprise replacements. There is huge gulf between the class, features, and bugs of products, even amongst the ones listed here.
Post #651170
Posted Thursday, February 5, 2009 4:47 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Thursday, November 13, 2014 2:52 PM
Points: 3,428, Visits: 14,451
Microsoft is looking for a few good BI developers to help with the next version of BI toolset.

This study starts on February 6 and runs till July 31. It will be a remote study and is open to all U.S.-based participants. We are looking for developers who are familiar with ETL, data warehousing, OLAP cubes, and MDX. We will be offering all participants a gratuity option in appreciation of your time. If you are interested in participating in this study please e-mail us at itusable@microsoft.com with "BI Developer" in the subject line.



Kind regards,
Gift Peddie
Post #651351
Posted Saturday, February 7, 2009 3:18 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Thursday, November 13, 2014 2:52 PM
Points: 3,428, Visits: 14,451
I just read some news that Sun is back to it old Solaris tricks again so MySQL founder quit that is not good. Sun needs the Linux and Windows running web hosting and developing users.

http://tech.yahoo.com/news/pcworld/20090205/tc_pcworld/mysqlcofounderquitssun





Kind regards,
Gift Peddie
Post #652307
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse