Microsoft SQL Server vs PostGIS

Need advice about which tool to choose?Ask the StackShare community!

Microsoft SQL Server

19.3K
14.9K
+ 1
540
PostGIS

372
368
+ 1
30
Add tool

Microsoft SQL Server vs PostGIS: What are the differences?

Introduction

In this article, we will discuss the key differences between Microsoft SQL Server and PostGIS. These two database systems have their own strengths and features that make them suitable for different scenarios. Understanding their differences can help developers and database administrators make informed decisions when choosing a database system for their projects.

  1. Spatial Data Handling: One of the major differences between Microsoft SQL Server and PostGIS is their ability to handle spatial data. While both databases support spatial data types and functions, PostGIS is specifically designed for handling and managing geospatial data. It provides advanced spatial functions, indexing capabilities, and support for various spatial data formats, making it an excellent choice for applications that heavily rely on geospatial data.

  2. License: Microsoft SQL Server is a proprietary database management system developed by Microsoft and comes with a commercial license. On the other hand, PostGIS is an extension of the open-source PostgreSQL database system and is released under the GNU General Public License (GPL). This means that PostGIS is free to use, modify, and distribute, making it a cost-effective option for organizations or projects with budget constraints.

  3. Community Support: Another significant difference is the level of community support and resources available for each database system. Microsoft SQL Server has a large and active community, with extensive documentation, official forums, and support from Microsoft. This ensures that users can find help, solutions, and updates easily. PostGIS, being an open-source project, also has a vibrant community, but the level of support might vary depending on the specific use case or project.

  4. Scalability and Performance: Microsoft SQL Server has features and optimizations specifically designed for handling large-scale databases, making it a preferred choice for enterprise-level applications with high volume and concurrency requirements. On the other hand, PostGIS, being an extension of PostgreSQL, inherits its scalability and performance capabilities. PostgreSQL has a reputation for excellent performance and can handle large datasets efficiently, making it suitable for a wide range of applications.

  5. Ecosystem and Integration: Microsoft SQL Server integrates seamlessly with other Microsoft products and tools, such as the .NET framework and Visual Studio. This makes it a favorable choice for developers already working with Microsoft technologies. PostGIS, on the other hand, integrates well with the PostgreSQL ecosystem and is compatible with various GIS software and libraries, providing flexibility and interoperability for geospatial applications.

  6. Platform Support: While Microsoft SQL Server primarily runs on Windows operating systems, it also has limited support for Linux distributions. PostGIS, being an extension of PostgreSQL, is compatible with a wide range of operating systems, including Windows, Linux, and macOS. This cross-platform support allows developers to deploy their applications on different environments without worrying about compatibility issues.

In summary, the key differences between Microsoft SQL Server and PostGIS include their spatial data handling capabilities, licensing model, community support, scalability and performance optimizations, ecosystem and integration options, and platform compatibility. Each database system has its strengths and considerations, and the choice ultimately depends on the specific requirements and constraints of the project.

Advice on Microsoft SQL Server and PostGIS

I am a Microsoft SQL Server programmer who is a bit out of practice. I have been asked to assist on a new project. The overall purpose is to organize a large number of recordings so that they can be searched. I have an enormous music library but my songs are several hours long. I need to include things like time, date and location of the recording. I don't have a problem with the general database design. I have two primary questions:

  1. I need to use either MySQL or PostgreSQL on a Linux based OS. Which would be better for this application?
  2. I have not dealt with a sound based data type before. How do I store that and put it in a table? Thank you.
See more
Replies (6)

Hi Erin,

Honestly both databases will do the job just fine. I personally prefer Postgres.

Much more important is how you store the audio. While you could technically use a blob type column, it's really not ideal to be storing audio files which are "several hours long" in a database row. Instead consider storing the audio files in an object store (hosted options include backblaze b2 or aws s3) and persisting the key (which references that object) in your database column.

See more
Aaron Westley
Recommends
on
PostgreSQLPostgreSQL

Hi Erin, Chances are you would want to store the files in a blob type. Both MySQL and Postgres support this. Can you explain a little more about your need to store the files in the database? I may be more effective to store the files on a file system or something like S3. To answer your qustion based on what you are descibing I would slighly lean towards PostgreSQL since it tends to be a little better on the data warehousing side.

See more
Christopher Wray
Web Developer at Soltech LLC · | 3 upvotes · 421.5K views
Recommends
on
DirectusDirectus
at

Hey Erin! I would recommend checking out Directus before you start work on building your own app for them. I just stumbled upon it, and so far extremely happy with the functionalities. If your client is just looking for a simple web app for their own data, then Directus may be a great option. It offers "database mirroring", so that you can connect it to any database and set up functionality around it!

See more
Julien DeFrance
Principal Software Engineer at Tophatter · | 3 upvotes · 421.1K views
Recommends
on
Amazon AuroraAmazon Aurora

Hi Erin! First of all, you'd probably want to go with a managed service. Don't spin up your own MySQL installation on your own Linux box. If you are on AWS, thet have different offerings for database services. Standard RDS vs. Aurora. Aurora would be my preferred choice given the benefits it offers, storage optimizations it comes with... etc. Such managed services easily allow you to apply new security patches and upgrades, set up backups, replication... etc. Doing this on your own would either be risky, inefficient, or you might just give up. As far as which database to chose, you'll have the choice between Postgresql, MySQL, Maria DB, SQL Server... etc. I personally would recommend MySQL (latest version available), as the official tooling for it (MySQL Workbench) is great, stable, and moreover free. Other database services exist, I'd recommend you also explore Dynamo DB.

Regardless, you'd certainly only keep high-level records, meta data in Database, and the actual files, most-likely in S3, so that you can keep all options open in terms of what you'll do with them.

See more
Recommends
on
PostgreSQLPostgreSQL

Hi Erin,

  • Coming from "Big" DB engines, such as Oracle or MSSQL, go for PostgreSQL. You'll get all the features you need with PostgreSQL.
  • Your case seems to point to a "NoSQL" or Document Database use case. Since you get covered on this with PostgreSQL which achieves excellent performances on JSON based objects, this is a second reason to choose PostgreSQL. MongoDB might be an excellent option as well if you need "sharding" and excellent map-reduce mechanisms for very massive data sets. You really should investigate the NoSQL option for your use case.
  • Starting with AWS Aurora is an excellent advise. since "vendor lock-in" is limited, but I did not check for JSON based object / NoSQL features.
  • If you stick to Linux server, the PostgreSQL or MySQL provided with your distribution are straightforward to install (i.e. apt install postgresql). For PostgreSQL, make sure you're comfortable with the pg_hba.conf, especially for IP restrictions & accesses.

Regards,

See more
Klaus Nji
Staff Software Engineer at SailPoint Technologies · | 1 upvotes · 421.1K views
Recommends
on
PostgreSQLPostgreSQL

I recommend Postgres as well. Superior performance overall and a more robust architecture.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Microsoft SQL Server
Pros of PostGIS
  • 139
    Reliable and easy to use
  • 102
    High performance
  • 95
    Great with .net
  • 65
    Works well with .net
  • 56
    Easy to maintain
  • 21
    Azure support
  • 17
    Full Index Support
  • 17
    Always on
  • 10
    Enterprise manager is fantastic
  • 9
    In-Memory OLTP Engine
  • 2
    Easy to setup and configure
  • 2
    Security is forefront
  • 1
    Faster Than Oracle
  • 1
    Decent management tools
  • 1
    Great documentation
  • 1
    Docker Delivery
  • 1
    Columnstore indexes
  • 25
    De facto GIS in SQL
  • 5
    Good Documentation

Sign up to add or upvote prosMake informed product decisions

Cons of Microsoft SQL Server
Cons of PostGIS
  • 4
    Expensive Licensing
  • 2
    Microsoft
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is Microsoft SQL Server?

    Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

    What is PostGIS?

    PostGIS is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Microsoft SQL Server?
    What companies use PostGIS?
    See which teams inside your own company are using Microsoft SQL Server or PostGIS.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Microsoft SQL Server?
    What tools integrate with PostGIS?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    JavaScriptGitHubNode.js+26
    20
    4934
    What are some alternatives to Microsoft SQL Server and PostGIS?
    Oracle
    Oracle Database is an RDBMS. An RDBMS that implements object-oriented features such as user-defined types, inheritance, and polymorphism is called an object-relational database management system (ORDBMS). Oracle Database has extended the relational model to an object-relational model, making it possible to store complex business models in a relational database.
    PostgreSQL
    PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.
    Apache Aurora
    Apache Aurora is a service scheduler that runs on top of Mesos, enabling you to run long-running services that take advantage of Mesos' scalability, fault-tolerance, and resource isolation.
    Microsoft Access
    It is an easy-to-use tool for creating business applications, from templates or from scratch. With its rich and intuitive design tools, it can help you create appealing and highly functional applications in a minimal amount of time.
    MariaDB
    Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.
    See all alternatives