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»»

A Look at MYSQL Expand / Collapse
Author
Message
Posted Tuesday, December 21, 2004 6:10 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 3:49 PM
Points: 2,866, Visits: 1,708
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/dpoole/alookatmysql.

LinkedIn Profile
Newbie on www.simple-talk.com
Post #152096
Posted Tuesday, January 04, 2005 2:02 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, May 10, 2006 4:00 AM
Points: 1, Visits: 1

It's a good article, showing the most logical way to connect to MySQL (ODBC)

To be complete however, I would suggest taking a look at Premiumsoft's NaviCat, which offers a more consistent connection to MySQL.

The main weaknesses of MySQL are the lack of procedure and trigger support, although some of this this has been added since V4 and V5 (Beta).

 

 




Post #153409
Posted Tuesday, January 04, 2005 2:09 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, October 23, 2008 2:57 AM
Points: 48, Visits: 50

until the production release of version 5, I cant consider mySQL anything more than a data store, and excellent solution if you want to just store historial audit data or similar, without having to pay for another SQL Server license.

the alpha release of mysql v5 is terrible.

 -- Alex

Post #153411
Posted Tuesday, January 04, 2005 6:43 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, April 17, 2014 1:24 PM
Points: 292, Visits: 255

The main weaknes is lack of foreign key support. Last I heard they never intend to implement it due to the performance hit. This is a DBA's nightmare!! To implement foreign keys in production or not is a business decision. If data integrity is not as important as performance, then fine, drop the FK's. In my experience, the benefits of data integrity have far outweighed any miniscule performance gain from not having FK's.

If you want a good, open source database system, look into PostgreSQL (PGSQL) and/or FirebirdDB. Both appear to be mature systems. The only reason PGSQL didn't beat out MySQL, imo, is from lack of marketing and a kind of smug attitude I have seen in their user community. Many of the posts I have seen in their newsgroups have had a distinct technology-bigot attitude. They recently changed their web site so maybe they are getting with the program now though

I haven't looked into FiredbirdDB very much but it looks like they have a nice community surrounding it and one of the originators of the system (when it was a commercial product) is currently in charge of it. Also, both DBMS' has .NET clients.



Bryant E. Byrd, BSSE MCDBA MCAD
Business Intelligence Administrator
MSBI Administration Blog
Post #153458
Posted Tuesday, January 04, 2005 9:26 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, March 21, 2014 7:45 AM
Points: 1,138, Visits: 698
And also, the licenses for both PostgreSQL and Firebird are a lot more leniant than MySQL -- you can get a good product GPL licensed, or you can pay for lack of data integrity... The choice is yours

--
Adam Machanic
SQL Server MVP
SQLblog.com: THE SQL Server Blog Spot on the Web
Post #153510
Posted Wednesday, January 05, 2005 7:20 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, January 25, 2006 9:53 AM
Points: 8, Visits: 1

I think the title is misleading - it's not about MySQL - it's about setting up the MySQL ODBC driver in Windows for DTS.

I'd call it - "DTS and MySQL" or "My adventures with DTS and MySQL" or "Don't read this if you want an overview of MySQL from the perspective of a SQL Server Admin"

Otherwise, nice article.




Post #153742
Posted Wednesday, January 05, 2005 11:53 AM


SSChasing Mays

SSChasing Mays

Group: Moderators
Last Login: Tuesday, February 18, 2014 7:51 PM
Points: 609, Visits: 406
Thanks for not trashing MySQL here. I am a hardcore MS SQL Server DBA I run two SQL Server users groups, but I've got a soft spot in my heart for MySQL I use it all the time and always have the current alphas,betas, or gammas loaded somewhere in my enviornment. I run a web site that sees 10k page hits a day all of them have between 2 and 20 querries on them. The box I run it on is a POS celeron 800 with 256 meg of ram and a single IDE hard drive. It still has room to grow! I tested the same setup with MS SQL Server and damn near killed the box just on memory footprint alone. I didn't need stored procs or triggers, and I'm broker than a stepped on cookie so MySQL was a perfect fit for me. The right tool for the right job. I've housed as much as 350GB of data on a single MySQL install. I to pushes and pulls using DTS all the time to MySQL and it works fine the article did outline the good gatchas.

Great article!


http://www.sqlserverio.com
http://www.cactuss.org
http://www.salssa.org
Post #153826
Posted Thursday, January 06, 2005 7:36 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 3:49 PM
Points: 2,866, Visits: 1,708
My first reaction to MySQL was that traditional databases cost money for a reason.

The more that I have used MySQL the more I find I like it although FK support, poor subquery support, lack of stored procedure support or triggers are draw backs.

However, MySQL was originally designed as an extremely fast output database for simple web applications and if you look at it from that perspective then it excels.

My first MySQL project involved using the www.x-cart.com shopping cart and for this appplication it was brilliant.

I think you have to look at any database system in the context of what it is designed to do and MySQL fits its niche brilliantly.

POSTGRES is interesting because it looks to be an open source ORACLE clone.


LinkedIn Profile
Newbie on www.simple-talk.com
Post #153991
Posted Thursday, January 06, 2005 7:41 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, March 21, 2014 7:45 AM
Points: 1,138, Visits: 698
MySQL is not free for any kind of commercial use.

That's the biggest misconception out there about it (other than people thinking that it's actually any good ). I wouldn't be surprised if most sites running MySQL are doing so in violation of the license, as they think it's a free product...

PostgreSQL and FireBird, on the other hand, can be freely used in any application AFAIK.


--
Adam Machanic
SQL Server MVP
SQLblog.com: THE SQL Server Blog Spot on the Web
Post #153996
Posted Thursday, January 06, 2005 8:26 AM


SSChasing Mays

SSChasing Mays

Group: Moderators
Last Login: Tuesday, February 18, 2014 7:51 PM
Points: 609, Visits: 406
from MySQL.com
The Commercial License is an agreement with MySQL AB for organizations that do not want to release their application source code. Commercially licensed customers get a commercially supported product with assurances from MySQL. Commercially licensed users are also free from the requirement of making their own application open source.

There is nothing in the documentation that says you MUST buy a commercial license unless you plan on violating the GPL in some way.

So, If you want to sell a product that is based on, distributes MySQL libraries or server components and don't want to release the source code to your product then you can buy a commercial license. Also, you can buy a commercial license if you want a direct legal relationship with MySQL AB.

You can run MySQL in your company all day long just like any flavor of Linux or any other GPL'ed software package.

So Adam, or anyone else that has questions about the dual licensing model I would suggest you read http://www.mysql.com/company/legal/licensing/commercial-license.html or contact MySQL AB directly like I did when I worked on my first commercial project with the prodcut.


http://www.sqlserverio.com
http://www.cactuss.org
http://www.salssa.org
Post #154026
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse