Over the years I have discussed the issue of Postgre SQL vs. Unless otherwise stated I am referring to Postgre SQL 9.3 and MS SQL Server 2014, even though my experience with MS SQL Server is with versions 2008 R – for the sake of fairness and relevance I want to compare the latest version of Postgre SQL to the latest version of MS SQL Server.
Each of these things, in isolation, may seem like a relatively minor niggle; however, the overall effect is that getting real work done in MS SQL Server is harder and more error-prone than in Postgre SQL, and data analysts spend valuable time and energy on workarounds and manual processes instead of focusing on the actual problem.
Update: it was pointed out to me that one really useful feature MS SQL Server has which Postgre SQL lacks is the ability to declare variables in SQL scripts. I wish it could, because there are an awful lot of uses for such a feature.
Microsoft no longer has the monopoly it once enjoyed on the desktop, thanks to the rise of Linux and Apple.
IT infrastructures are increasingly heterogeneous thanks to the flexibility of cloud services and easy access to high-performance virtualisation technology.
If Postgre SQL says your import worked, then it worked properly.
The slightest whiff of a problem and it abandons the import and throws a helpful error message.
Cross-platform software is about giving the user control over their infrastructure.
(At work I currently manage several Postgre SQL databases, some in Windows and some in Ubuntu Linux.
number of characters) of the last column in this file (it has 50 columns). (The answer you're looking for is exactly 183.895.) Naturally, determining this is trivially easy in Postgre SQL – in fact, the most time-consuming bit is creating a table with 50 columns to hold the data.
Poor understanding of CSV seems to be endemic at Microsoft; that file will break Access and Excel too.
Maybe MS SQL Server kicks Postgre SQL's arse as an OLTP backend (although I doubt it), but that's not what I'm writing about here, because I'm not an OLTP developer/DBA/sysadmin. Do please use it if you wish; I will do my best to respond. This section is a comparison of the two databases in terms of features relevant to data analytics.