MySQL vs MsSQL

Anon

Hey

how is MySQL performace vs MsSQL.

we a going to create a website wich will recive a lot of hits daily(A LOT), what is the best DB to go with, i have made a lot of things in MySQL and found it to be ok, but can it handle the high presure, or is it better to go with a MsSQL server or something compleatly different.

is there some links to sites comparing DB's?
what is your idea of different DB's ?
wich DB/Setup is best for highload sites?

we expect to have 40K+ user daily when compleated

Anon

Unfortunately, real, unbiased reviews of multiple RDBMSs are hard to come by.

Part of the problem is that a substantial portion of the performance of the DB is/can be tied to the underlying O/S and hardware platform.

MySQL is fine if your hits are going to be mostly select statements - it's heavily optimized for this.

PostgreSQL is often better when you are doing more write type transactions, since PG supports, among other things, transactions (reason enough to go with PG, it's a VERY useful feature!)

I've heard a fair amount about MsSQL, most of it bad, but I've never developed on it, worked with it, or paid much attention since I devel on Linux, so I really don't have much to say there.

And that is part of the problem. How many people can really compare Oracle against Postgres, Oracle against MsSQL, Postgres against MsSQL, against MySQL, on all the different platforms, and actually come up with an "unbiased" opinion?

If it were my call, I'd recommend MySQL if you are doing mostly reads, (select ...) and either PostgreSQL or Oracle ($$$) if you are doing more writes (insert into... update...)

MySQL, from what I've seen, is the DB best integrated into PHP.

Oh, and if you are serious about the loads you plan on working under, use Unix. Windows just doesn't handle the load as well and is not as scalable as a well-tuned *nix.

-Ben

Anon

just a comment:

Don't try to compare Mysql with Oracle

think this:
BMW one of the best cars available today but if you compare it with Porche is just a common car :-)

just use the appropriate db for your specific needs and the money you have

Anon

Oh, but you are missing the point!

I don't think we're trying to compare a BMW to a Porsche here, it's more like comparing a BMW to a Pickup!

They DO and CAN BE compared!

What makes BMW a "regular car" when compared to a Porsche?

If that's the case, then either
1) BMW is severely over-rated
2) You aren't really comparing the
two on the merits of what they really are.

BMW has a very good reliability and safety record. (unparalleled) Porsche is a fast car
with a crummy reliability record.

What are you comparing?

Anon

Every database has some advantages and some disandvantages.
1. the main advantage of MySQL? it's FREE!
2. the only disadvantage of Oracle? is costs a lot of money

so
-for a guy who just wants to publish some content over the Internet
MySQL is the preffered DB
- for a company with requirements the best choice is Oracle.

Anyway,
Your post gaves me a starting point for a good conversation :-)
so,
i put some (AND THERE ARE MANY MORE BELIEVE ME) features of "Porche" here :-)

ORACLE Features

1.- "Object creation & manipulation" instead of table creation (Object oriented db)
2. Partition Tables
3.
4. Java store procedures (with support for web)
5. Pl/sql stored procedures (with support for web)
6. Intentional Index Suppression (Optimizer level ex.
- / FULL / BLOCKS
- /+ INDEX(table_name index_name1 index_name2...) /
- /+ ORDERED / and many other

sequences
8 synonyms
datafile (table space ) administration (create your space before put your schema on it
rollback segments
function based indexes
Index Joins
Materialized Views
Hash/Composite Partitioning
Partition-wise Joins
CUBE and ROLLUP
Top N Queries capabilities
Random Sampling
Direct-Path Load API
Ftee text search capabilities
Parallel Execution Statement Processing (using paraller DMLs)
SQL extented syntax (i.e for self join manipulation : Connect by prior)

etc, etc etc

LET'S SEE IF MYSQL SUPPORTS THEM :-)

Anon

Well geez - I mean, if I'm going to invest the time to put forth my views, I might as well comment on their result, eh?

I hate MySQL. It's a pitiful database with so few features and so many limitations that it drives me utterly mad.

It's fairly easy to set up, so if your needs are VERY modest, it's a good choice.

It's great in areas where the reliability of the data isn't super high. (IE: what's the disaster if a write didn't happen?)

PostgreSQL supports transactions, and has a very full feature set, I like it best. (formula being $best=$bang/$buck)

It's also completely open-source, like (it appears) that MySQL will finally be.

Of course, it has its own problems (8k record limit, anyone?) but I've not run into these much. (Don't store large objects in a database!)

My $0.02.

-Ben