MySQL vs SQL Server

Title says it all, which is better and why? Are either better at all? Which does x task better?

FOSS vs proprietary aside.

Other urls found in this thread:

postgresql.org/docs/9.6/static/features.html
postgresql.org/about/featurematrix/
microsoft.com/en-us/sql-server/sql-server-2016-editions
twitter.com/AnonBabble

> ms SQL
>kek

Great post

Mysql is shit all over. At least mssql is very good/fast at some things..

Depends a bit on what you are doing. Just a small website, MYSQL. Need enterprise scalability and don't mind a bit of a learning curve, sql server. Need to experiment, Mongo dB.

MariaDB

>Need enterprise scalability and don't mind a bit of a learning curve
Oracle

PostgreSQL

In 99% of cases Sqlite is totally anyone needs.

This. Not only is PostgreSQL free, it is also feature complete (JSONB data type, anyone?), and has sane defaults.

Documentation's pretty nice, too.

The only reason MySQL is still being used is due to word of mouth, which is quite disappointing.

MySQL is the PHP of databases, MSSQL is the VB.NET.

I honestly just use what tutorials tell me to use.

>MySQL
Use MariaDB instead.

OP here. I ask because I'm in a uni course where we're using MySQL as our db for the semester. I'd like to develop good habits while learning that can translate to other DBMS.

>PostgreSQL
winrar

nononononono
You see mane, you are learning the basics of the kiddie stuff there, thats what most college courses are.
Of course there is some common ground among DBMS, but beyond that, you'll have to learn and adapt with every one of them.

You want MSSQL, you'll need to learn Transact SQL, you want Oracle? PL-SQL You want MySQL you'll need to learn their SQL flavor too.

MySQL is comfy and a good place to start, and grab some concepts.

You can experiment with Express editions of MSSQL to quench your thirst if you want to, comes with documentation too (called books online), just read about which version you are downloading

They are for different uses.

MS-SQL is comparable with PostgreSQL in the FOSS world and Oracle .

You just need to learn SQL for Uni. Although it's the single language with the most dialect I've known, the basics cover everything you'd need for a developers/user standpoint. If you want to become a DBA then you'd need to go way deeper though.

>as soon as you need more than one server, you're fucked

>it is also feature complete
not really, but then again, SQL standard is inane in quite a number of parts

Just use mariadb you cunt. You don't have to get dicked by oracle.

Pretty much this but as far as I remember mysql is faster when dealing with simple crud operations, postresql is way faster with dealing with complicated queries.

The only correct answer

That's when you want an enterprise system plus not only getting dicked by Oracle (as with MySQL community edition), but also their licensing.

It's fully compatible with SQL-2008 and there's work already on supporting SQL-2011 ad SQL-2016. There are also many additional features exclusive to PostgreSQL.

postgresql.org/docs/9.6/static/features.html
postgresql.org/about/featurematrix/

I'm a fan of MS Sql. In their newest version they added support for JSON columns and temporal tables for easy history change tracking of tables.

Between those two I'd pick MariaDB (MySQL fork by the core MySQL devs) any day of the week.

MSSQL you choose only at gunpoint.

Am I the only one who thinks Postegree's "clusters" are too complicated and the documentation kinda sucks?

FoundationDB. I still have a copy.

none of them are even usable

one is heavily integrated into M$ shit so badly that in order to run it on loonix, M$ had to write their own NTism kernelspace in userspace to make it fucking work.

MySQL is technically FOSS but that hasn't stopped Oracle for randomly sueing people for using it over their licensed Oracleware 12c cancer that belongs in 1985.

this thread is shit, like you OP. fuck off.

Your database abstraction should be configurable to use a number of different engines.

Stubborn clients that want you to piggy back off an existing rac/other sql cluster?

not an issue. Plus, this means integrating with other applications easy if the transport method is via a db. Instantiate a new db object with connect with new cdn information and bam, your query tools that you're familiar with are available at hand.

sql server v.next will work on linux, no problem whatsoever

So what is your dvice

sql server any day

If you're using SQLite you know you'll never need more than one server. Hopefully you're using an ORM and can easily switch to something else if needed.

BI developer here.

wow. someone is actually talking about sql on Sup Forums.

mysql is the vanilla ice cream. it's plain, boring, FREE, feature poor, so it's what you get when you have to bring ice cream to a public gathering. it'll do everything you need, but it won't do it well, and writing code for it is a chore. best feature: free.

sql server is well rounded, easy to use, NOT free, lots of advanced features (great for a small to mid sized data mart), but it doesn't really scale up to enterprise sized applications. you'll more likely see oracle in those scenarios. small/mid size deployments this is probably the most enjoyable.

large corps usually have plenty of windows servers to go around for active directory, exchange, sharepoint etc so this is probably only a problem for small orgs

>Are either better at all?
MSSQL

>which is better and why?
Because Oracle is Oracle's actual enterprise class database. Who the fuck uses paid for editions on MySQL? No one. Just look at things like MSSQL's profiler or sparse columns.

>Express editions of MSSQL
Just pirate the MSDN copy of it.

There's no official PostgreSQL solution for clustering anyway.

Well, MSSQL Express is free, or as free as MS wants to allow it.

Its a great place to tinker with MSSQL without give'em the shekels. Its even usable in some small production scenarios.

There are even some MS products like WSUS that require MSSQL, but before shitting your pants you install an Express MSSQL and you are done.

Wnat to do a small project that you know it wont use a lot of DB space and you need MSSQL? Express has you covered.

B-b-b-b-b-but MS giving tous for free? Well they want you to get used to their stuff so the probabilities increase that in your next project you consider using their stuff, but its a fair trade off.

As far as I remember you dont get the most advanced stuff from express editions like built-in BI stuff

microsoft.com/en-us/sql-server/sql-server-2016-editions

>Blah blah blah MS shilling yadda yadda
OP wanted to know the difference, and its not nice to close up to options in college

>>Blah blah blah MS shilling yadda yadda
>OP wanted to know the difference, and its not nice to close up to options in college
exactly, it seems like a lot of people don't have a lot of real world exp with databases too, just from tinkering around with small projects. I work in a massive org so we have thousands of data marts, from small to "big data" large, and none of them are on FOSS engines.

Best GUI app for visually creating SQL queries?
Should be easy to use and not require sql knowledge.

you're retarded if you cant write SQL

I can but researchers can't. The alternative would be that I implement it myself but surely there must be already existing solution.

>I can but researchers can't. The alternative would be that I implement it myself but surely there must be already existing solution.
SQL is designed for normies to use. If they can't understand joins, aggregrates and conditions, a GUI wont help them.

Yes but women get scared when they see "sql code". Also I already told them to learn sql but but they told me no.

It's now part of the job for them. They can either learn it or fuck off.

Then tell them to get fucked and tell their bosses to hire competent employees.

>Best GUI app for visually creating SQL queries?
Don't even go there, most of them are way less user friendly then just writing the SQL yourself. Select statements are not hard.

What do you think about stored procedures?

MSSQL is nice in that it is easy to write CLR stored procedures with full access to the .NET API so you can do tons of stuff which you cant easily with MySQL.

SQL Server is the better of the two, but the usage case for both is very different. Oracle is even better then them both, and I'd argue the king of databases. NoSQL solutions like Mongo are a meme that only are useful in extremely niche circumstances, and you should fire anyone who suggests replacing your ACID compliant database with Mongo.

You guys know MySQL is oracles db software right? You're not retarded are you?

Yes

This

>none of them are usable
>used by millions of websites flawlessly everyday

Think you're the problem

they are all shit, just learn the language

>You guys know MySQL is oracles db software right? You're not retarded are you?
pretty sure you're the retard friend if you think mysql and oracle are similar in any way

I have a BI chick at work and I just explained her how to google and basics of joins, group by etc and now she's fluent in MSSQL and she started to learn python to automate reporting and R for fancy graphs and I'm kind of proud of her. Just try to explain to them why SQL is a must have and if they don't get it tell them to fuck off because they won't handle this job.

>There are even some MS products like WSUS that require MSSQL
WID works with it which is basically a even lower end version of SQL Server Expression.

>>Express editions of MSSQL
>Just pirate the MSDN copy of it.
Just get developer edition, it's free.

Since this is kind of a sql thread, how can I torture test my database if It only has a handful of concurrent users? I don't have access to a production server yet.

>You guys know MySQL is oracles db software right? You're not retarded are you?
Are you? MySQL was built by SUN and was left to death in Oracle, why the hell would MariaSQL exists otherwise?

Oracle Database is completely different than MySQL

From my experience with both I can say each has pro's and con's. If I had a gun against my head I would say that MSSQL is the better database. For ease of management and in my expedience MSSQL had more available backend/ODBC support from the other software we used.

We actually tried to move our DB to MySQL and in the process inevitable failed because it was so slow with the data we were using. Chose to go with postgres instead!