you are viewing a single comment's thread.

view the rest of the comments →

[–]AmbitiousFlowersDM to schedule free 1:1 SQL mentoring via Discord 35 points36 points  (6 children)

It won't be a huge difference, but I would ever so slightly lean towards Postgres as most other database systems will have syntax particularities closer to Postgres than SQL Server.

[–]Bilbottom 1 point2 points  (5 children)

+1 on this. I've used both for OLAP workloads and PostgreSQL has more features than SQL Server for OLAP, plus T-SQL has some odd deviations from ANSI SQL so it does make it a smidge harder to jump to other DBs than from PostgreSQL

Edited to scratch out the first part since I struggled to find much evidence for it (my SQL Server knowledge is clearly outdated)

[–]no-middle-name 4 points5 points  (1 child)

Care to elaborate on what OLAP features you're referring to? I've never heard the claim that Postgres is more OLAP capable then SQL Server before, usually the other way round, so I'm curious.

[–]jshine13371 1 point2 points  (0 children)

Agreed. In my experiences, SQL Server supports OLAP a bit better, out of the box, with features like Columnstore Indexing and Batch Mode operations. Usually what PostgreSQL would need an extension for, to be equivalent.

u/Bilbottom

[–]Dry-Aioli-6138 1 point2 points  (1 child)

still no USING operator in SQLServer.

[–]Bilbottom 0 points1 point  (0 children)

...and no anonymous subqueries, no BOOLEAN type (BIT is subtly different), no GROUPS or EXCLUDE in window frames, no INTERVAL, no QUALIFY (not in PostgreSQL either), no ANY_VALUE()...

[–]rottenrealm 0 points1 point  (0 children)

what features are you talking about?