Heroku Postgres vs Microsoft SQL Server

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

Heroku Postgres

334
296
+ 1
38
Microsoft SQL Server

15.5K
11.5K
+ 1
539
Add tool

Heroku Postgres vs Microsoft SQL Server: What are the differences?

Developers describe Heroku Postgres as "Heroku's Database-as-a-Service. Based on the most powerful open-source database, PostgreSQL". Heroku Postgres provides a SQL database-as-a-service that lets you focus on building your application instead of messing around with database management. On the other hand, Microsoft SQL Server is detailed as "A relational database management system developed by Microsoft". Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

Heroku Postgres belongs to "PostgreSQL as a Service" category of the tech stack, while Microsoft SQL Server can be primarily classified under "Databases".

"Easy to setup" is the primary reason why developers consider Heroku Postgres over the competitors, whereas "Reliable and easy to use" was stated as the key factor in picking Microsoft SQL Server.

According to the StackShare community, Microsoft SQL Server has a broader approval, being mentioned in 470 company stacks & 425 developers stacks; compared to Heroku Postgres, which is listed in 74 company stacks and 38 developer stacks.

Advice on Heroku Postgres and Microsoft SQL Server

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
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
Julien DeFrance
Principal Software Engineer at Tophatter · | 3 upvotes · 191K views
Recommends
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
Christopher Wray
Web Developer at Soltech LLC · | 3 upvotes · 191.4K views

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
Recommends
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 · 191K views
Recommends
PostgreSQLPostgreSQL

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

See more

Considering moving part of our PostgreSQL database infrastructure to the cloud, however, not quite sure between AWS, Heroku, Azure and Google cloud. Things to consider: The main reason is for backing up and centralize all our data in the cloud. With that in mind the main elements are: -Pricing for storage. -Small team. -No need for high throughput. -Support for docker swarm and Kubernetes.

See more
Replies (2)
Max Musing
Founder & CEO at BaseDash · | 1 upvotes · 31.6K views

DigitalOcean's offering is pretty solid. Easy to scale, great UI, automatic daily backups, decent pricing.

See more
David Weinberg

Good balance between easy to manage, pricing, docs and features.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Heroku Postgres
Pros of Microsoft SQL Server
  • 29
    Easy to setup
  • 3
    Follower databases
  • 3
    Dataclips for sharing queries
  • 3
    Extremely reliable
  • 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
    Always on
  • 17
    Full Index Support
  • 10
    Enterprise manager is fantastic
  • 9
    In-Memory OLTP Engine
  • 2
    Security is forefront
  • 1
    Columnstore indexes
  • 1
    Great documentation
  • 1
    Faster Than Oracle
  • 1
    Decent management tools
  • 1
    Easy to setup and configure
  • 1
    Docker Delivery

Sign up to add or upvote prosMake informed product decisions

Cons of Heroku Postgres
Cons of Microsoft SQL Server
  • 2
    Super expensive
  • 4
    Expensive Licensing
  • 2
    Microsoft

Sign up to add or upvote consMake informed product decisions

What is Heroku Postgres?

Heroku Postgres provides a SQL database-as-a-service that lets you focus on building your application instead of messing around with database management.

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.

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

Jobs that mention Heroku Postgres and Microsoft SQL Server as a desired skillset
CBRE
United States of America Texas Richardson
What companies use Heroku Postgres?
What companies use Microsoft SQL Server?
See which teams inside your own company are using Heroku Postgres or Microsoft SQL Server.
Sign up for StackShare EnterpriseLearn More

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

What tools integrate with Heroku Postgres?
What tools integrate with Microsoft SQL Server?

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

Blog Posts

GitHubPythonNode.js+47
53
70420
GitHubPythonSlack+25
7
2951
GitHubPythonDocker+24
13
16814
What are some alternatives to Heroku Postgres and Microsoft SQL Server?
MongoDB
MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.
ClearDB
ClearDB uses a combination of advanced replication techniques, advanced cluster technology, and layered web services to provide you with a MySQL database that is "smarter" than usual.
Heroku
Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.
Google Cloud SQL
MySQL databases deployed in the cloud without a fuss. Google Cloud Platform provides you with powerful databases that run fast, don’t run out of space and give your application the redundant, reliable storage it needs.
Heroku Redis
Heroku Redis is an in-memory key-value data store, run by Heroku, that is provisioned and managed as an add-on. Heroku Redis is accessible from any language with a Redis driver, including all languages and frameworks supported by Heroku.
See all alternatives