MySQL or MSDE

[sharpcoder]

Good evening (and in case you're somewhere else in the world good night and good morning...)!

 

At present I'm using MySQL as DBMS in my web app but I'm having second thoughts...

 

A guy I talked to said that MSDE would boost performance in my case and that even though it's just a budget version of MS SQL it can do a lot more that MySQL and better too.

 

So... Is he lying?

Edited January 5, 2004 by sharpcoder

[samsmithnz]

Probably not. MYSQl's advantages are that its small and runs on crossplatforms. MSDE is probably quite a bit quicker, but you'll obviously need a windows server, and these are generally more expensive than a Linux/Unix based one.

[sharpcoder]

quite a bit quicker

 

That's the interesting part. How much quicker?

Is it stable (more than mysql?)?

Can I use the same SQL for MSDE as I have used for MySQL?

Thank you.

[samsmithnz]

That's the interesting part. How much quicker?

Is it stable (more than mysql?)?

Can I use the same SQL for MSDE as I have used for MySQL?

Thank you.

 

I'm not sure how much faster, I've never tryed to compare them side by side.

 

Its probably just as stable as MSDE (which has its good and bad days)

 

MOST SQL will be the same, but you'll have to throughly test everything. Again, I've never writen more than basic insert, update and select statements on MYSQL, but I know for example that SQL joins have quirks between Access and SQL server.

[sharpcoder]

Then I don't think the SQL code will be a major problem in my case.

Otherwise... is the general suggestion that I should change DBMS from MySQL to MSDE?

[samsmithnz]

I'm not making that suggestion at all, its up to you to make a decision based on your situation. There are plenty of articles online:

 

Here's one that may affect you:

 

http://dbforums.com/arch/5/2003/3/698728

 

It states that MSDE only allows 5 connections. Why? Cos its free. They want you to buy SQL 2000.

 

(If found several articles in Google by just typing MSDE vs mysql

[sharpcoder]

Thank you samsmithnz for googling.

I think I'll stick to MySQL for now and see what future brings...

[irasmith]

I'll add my two cents worth to this discussion, for whatever you might consider the adivce worth.

 

I wouldn't say really that one product is better than the other. I have never had the good fortunes of having two servers side by side to run speed tests or other benchmarks, so I have no clue as to which one is truly fastest under test conditions.

 

At least for me, I let the situation at hand govern what tools I use. MySQL is a good product, it is stable, and it has the vantage of being free if you don't happen to fall into the categories that require the purchase of a commercial license. I won't get into that discussion, you can simply look at their site and see what the license terms are to determine your status.

 

MS SQL is also good, it is stable, and at least the MSDE version is what I call 'near free' in that it's price is substantially less than the fully blown SQL 2000 price. I do believe there is a connection limitation on it as really the MSDE version is supposed to be used by developers in a development environment, not as a production application by everyone that works in the company.

 

MySQL can't do some of the things that MS SQL can though. For instance, if you need to use Views or Stored Procedures, you will need to use MS SQL as MySQL doesn't have these features as of this time. In future releases these items are planned, again just check out the MySQL site for what is in store for future development of the product.

 

So when you look at the decision of what to use or what to stay with, personally I would think in terms of what my future needs will be and what product has or will have those things to fill my needs as they come about.

 

I hope this helps you out and I wish you the best of luck.