r/programming • • Nov 16 '14

PostgreSQL vs. MS SQL Server - A comparison of two relational databases from the point of view of a data analyst

http://www.pg-versus-ms.com/
171 Upvotes

321 comments sorted by

View all comments

Show parent comments

58

u/[deleted] Nov 16 '14

We all know I like PostgreSQL better, that's obvious

It's obvious, but not from the title. Based on the title, I was expecting a balanced article and didn't see one. Reflect your preference in the title, and I'll have no problem with the article.

-19

u/squareproton Nov 16 '14

If by "balanced" you mean having the same number of pros and cons for each database, then no, it's not balanced - but that is because (IMHO) PostgreSQL really is an objectively better database.

So even though I say loads of good things about PostgreSQL and loads of negative things about MS SQL Server, I don't think I'm being biased or unfair or prejudiced - I'm just neutrally reporting what I see as a really good database compared to a really mediocre one.

If you disagree, hopefully it is because your experiences with these databases are different to mine, and not because my style of writing makes you think I'm a fanboi...

13

u/Johnno74 Nov 17 '14

I have no experience with PostgreSQL, I've heard nothing but good things tho and I'd like to use it in a project someday but I work at a MS shop. I've used MySQL and hated every second.

But I didn't even bother to read all of your blog post, because after about 10 seconds of scrolling it was obvious that you don't are nowhere hear knowledgeable enough about MS SQL server to be comparing it against anything. The first thing I scrolled to was a critique of SQL server talking about the transaction log filling the disk, and you phrased this as a "bizzare failure mode". Seriously, this is SQL server 101 stuff. If you don't know why that happened, or how to fix it then you really shouldn't be going near a production DB.

I then saw for example under "scriptability" you say MS SQL Server is driven through a GUI" which is completely false. Yes, there is a GUI, but you can do everything that the GUI does + tons more from a SQL command line - Under the hood the GUI is just sending tsql commands to the server. If you want there are command-line utilities to send that tsql to the DB direct from the windows command line, a plain text file, pretty much anything.

And then you say "(Who on Earth wants a GUI on a server anyway?)" - if you are logging onto the server's desktop to run the gui there ON the server then... you clearly have a LOT to learn. Seriously, run the GUI on your workstation and connect to the server thru the gui. Or just use the command line, or any other tool you like to remotely admin the server.

I could go on. you said " MS SQL Server, a CREATE PROCEDURE statement cannot appear halfway through a batch of SQL statements." Completely false - you just need a "GO" statement between the preceding statement and the "create procedure" statement.

Sorry, your comparison looks like uninformed MS bashing. If you don't know how to use the tool, don't blame the tool.

27

u/judgej2 Nov 16 '14

If by "balanced" you mean having the same number of pros and cons for each database

No, I don't think you get bias. Why not just present the facts. If there are a bunch of features that are comparable, but use different commands, then then can be listed in a table. They do the same thing, and use different statements - fine. But the MSSQL commands are then picked apart as being silly, or mysterious, or really silly because you need to comment something out to make them to something different.

Anyway, judging by your other replies, you are not in the slightest interested in what we think of your article and why, so I'll just leave that there and you can do what you like.

-28

u/squareproton Nov 16 '14

Well, it was never my intention to just provide a table of facts - I've added my opinion too.

Can't really win against your second point - if I agree with you I'm admitting I don't care what anyone thinks, and if I disagree then you'll say I don't care what you think...

(actually I do care what people think)

17

u/[deleted] Nov 17 '14

From both the domain name - pg-versus-ms.com - and the title of your submission I would expect a more or less objective "here's the workloads where Postgres is better; here's the workloads where MS SQL is better; here's how to choose between them".

Instead, you're talking about why Postgres is awesome, using MS SQL as a strawman to compare it against. If you want to brag about how much you love Postgres, register postgresisthefuckingshit.com and go at it.

I'm a fan of Postgres as well, FWIW (though since I live in the Linux world, I'm usually singing its praises compared to MySQL). But you're being intellectually dishonest.

-1

u/squareproton Nov 19 '14

From both the domain name - pg-versus-ms.com - and the title of your submission I would expect a more or less objective

Well, sorry, but your attempt to guess the contents of the article based on the domain and title failed. That's not my fault. I put an intro explaining what I was trying to do right there at the top of the page. Sounds like you've decided what you wanted before you even read the page and now you're disappointed that you guessed wrong.

There's no straw man here - every time I talk about an inconvenience, bug or failure mode of MS SQL it's either from personal experience or from the Microsoft docs.