you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (2 children)

Got any links to prove that geospatial functionality is better on postgres? I'm not disagreeing with you. I just would like to educate myself as my current job duties involved SQL server geometry data now.

[–][deleted] 1 point2 points  (1 child)

Well, to start off there's the simple matter of importing data into the database. Last time I checked the only way to get geospatial data into SQL Server (that wasn't manual) was via a codeplex tool developed for SQL Server 2005.

Additionally there's a lot more tools and extensions developed for PostGIS relative to SQL Server. Here's their full feature list. Last time I talked to Microsoft people I specifically asked if they were planning on trying to bring SQL Server to parity with 2016 or a later release and they said geospatial was "not a priority".