PostgreSQL vs. Azure SQL Database

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
PostgreSQL
Score 8.8 out of 10
N/A
PostgreSQL (alternately Postgres) is a free and open source object-relational database system boasting over 30 years of active development, reliability, feature robustness, and performance. It supports SQL and is designed to support various workloads flexibly.N/A
Azure SQL Database
Score 8.3 out of 10
N/A
Azure SQL Database is Microsoft's relational database as a service (DBaaS).
$0.50
Per Hour
Pricing
PostgreSQLAzure SQL Database
Editions & Modules
No answers on this topic
2 vCORE
$0.5044
Per Hour
6 vCORE
$1.5131
Per Hour
10 vCORE
$2.52
Per Hour
Offerings
Pricing Offerings
PostgreSQLAzure SQL Database
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
PostgreSQLAzure SQL Database
Considered Both Products
PostgreSQL
Chose PostgreSQL
My expirence with other solutions is very limited, but what I saw/heard is, that on Azure the managed MS SQL Server is said to be more flexible and you can use it in a serverless-ish fashion. But on the other hand, PostgresSQL is still strong regarding its efficiency. And in my …
Chose PostgreSQL
Being open source, PostgreSQL offers the highest performance among its peers. It has a strong support community where we can find solutions to most of the queries. It's suited for GIS (Geospatial) based applications, making it unique from its peers. There are fewer databases …
Chose PostgreSQL
We had to use PostgreSQL as that is the DB preferred by our SaaS Provider.
Chose PostgreSQL
PostgreSQL holds it own against both these options. Some of these DBs are in play for certain needs but the majority are PostgreSQL because of cost and operational performance.
Chose PostgreSQL
In my experience using all of these products over many years, PostgreSQL is better than any of them in reliability, performance, productivity, cost, scalability and interoperability across operating systems.
Chose PostgreSQL
MySQL is an Oracle product which has in itself some known issues due to that (support, contract terms). Based on my knowledge, PostgreSQL support everything that MySQL support (syntax wise) and it adds more improvements and syntaxes that make the life of database engineers and …
Chose PostgreSQL
First It's open source and it's cost-effective compared to other databases.PostgreSQL can be easily integrated with numerous platforms. It is well known and appreciated so relying on it as our system database can be easily accepted by our customers. And if your developing a …
Chose PostgreSQL
For our use cases, PostgreSQL is just as feature rich as other options, costs less, and is simple to get up and running. There is also a plethora of documentation to support it which makes it a great option for a small scale startup without needing high levels of expertise to …
Chose PostgreSQL
In this case, Postgres is preferred because it handles large data sets and requires fewer hardware resources than its competitor, MySQL. Compared to PostgreSQL, Microsoft products are excellent, but the installation process for MS SQL is lengthy. PostgreSQL has an advantage …
Chose PostgreSQL
I've been using different databases for the past 20 years, solutions like MS SQL Server, MySQL, MariaDB, Interbase, Firebird, DB2, etc., and by using them I wasn't able to be neither close to the performance PostgreSQL deliver. Also, it is one of the most popular databases on …
Chose PostgreSQL
Although the competition between the different databases is increasingly aggressive in the sense that they provide many improvements, new functionalities, compatibility with complementary components or environments, in some cases it requires that it be followed within the same …
Chose PostgreSQL
We evaluated both PostgreSQL and MySQL, two popular open source relational databases. While they are very similar in most areas, PostgreSQL's reliability and performance won us over, plus it has much better support from cloud vendors we also work with.
Chose PostgreSQL
Postgres stacks up just [fine] along the other big players in the RDBMS world. It's very popular for a reason. It's very close to mySQL in terms of cost and features - I'd pick either solution and be just as happy. Compared to Oracle it is a MUCH cheaper solution that is just …
Chose PostgreSQL
A free corporate professional product. Who does not want to have such a thing, we hesitated because we did not know the product before and frankly we did not want it at first. But when we give it a chance, it has been running smoothly for years.
Chose PostgreSQL
When we were originally evaluating Redshift we ran into some issue with dates. Either way, Postgres is a better choice than Redshift because it avoids vendor lockin. We ended up choosing Postgres over MySQL because it was easier at the time to get a hosted Postgres cluster up …
Chose PostgreSQL
As I have been telling all along, PostgreSQL is much cheaper compared to the other RDBMS solutions. It has got better performance with some of the application services that we are using and is easy to maintain. Overall, we are satisfied migrating to PostgreSQL database clusters.
Chose PostgreSQL
Much more mature and stable when compared to MySQL with features such as MVCC, complex subquery plans, ORDBMS, and NoSQL support. With Oracle retaining rights to MySQL its future as an open database is less secure and is no longer in the hands of the community. PostgreSQL also …
Chose PostgreSQL
Its main characteristic is the integrity of the data. In addition, being free software, it has no costs associated with its license, which allows the number of installations to be scaled without problems.
The technical staff quickly learns about its installation, configuration …
Chose PostgreSQL
Both Oracle and MS-SQL database option fell when we evaluated the effect on our overall solution cost to our customers. customer examine the overall cost of the solution they buy, selecting Oracle or MS-SQL would leave less money in our pockets.
We are Linux based solutions and …
Chose PostgreSQL
PostgrPostgreSQL as a transaction db engine against oracle and sql server works well. TPM wise compared to MySQL and MariaDB, on an evan scale.
SQL function supports, far outweighs compared to MySQL and MariaDB. PG Extensions allow for flexibiltity and scalability. Allows …
Chose PostgreSQL
We selected PostgreSQL due to the number of employees who have used it in the past.
The data consistency guarantees.
The multiple transaction isolation levels support.
Chose PostgreSQL
PostgreSQL outperforms every other option. It is faster, more flexible, more reliable, easier to maintain, and more consistent in behaviour than any of the other offerings.
Chose PostgreSQL
The main reason for select PostgreSQL against MS SQL Server Express edition is the necessity to use open-source platform, without any issues for licensing, client licensing, etc. etc, which is usually follows developers and project managers when they start to use products and …
Chose PostgreSQL
I think Postgres stacks up great against all modern database solutions and has continued to be a trend leader in this space.
Azure SQL Database
Chose Azure SQL Database
Better and more useful automation tools are available. Better at scaling and hosting your data. Greater security around access of data and encrypting where required. Allows for seamless integration in other Azure solutions which allows for greater flexibility when using the …
Chose Azure SQL Database
Depending on the use case they stack up very well. Google and AWS are well suited multi-cloud strategies or those that need a high level of RDS performance.
Chose Azure SQL Database
Mainly response time. Azure SQL Database is very fast and very reliable when it comes to executing queries and gathering the data results. Also, the exporting options it gives are far exceeding expectations and enable users to accommodate any deliverable in a timely and …
Chose Azure SQL Database
I selected Azure SQL because it integrates nicely with the technology stacks we currently maintain. The pricing is right, and clients are happy with that. Scaling is easy. Most of our clients don't want to maintain a full-blown database server, and they don't need one. For …
Chose Azure SQL Database
We have selected it because we are using Azure Cloud and it is the best option for us to go ahead with Azure SQL Database.
Chose Azure SQL Database
The simplicity and great features and good support of Microsoft as well as the more reasonable flexible price than other competitors is one of the important reasons for choosing it.
Chose Azure SQL Database
Oracle database is "the" serious database. There really is no competition in that field. SQL Database would be a serious competitor through the ease of implementation and the "no maintenance," but since it's too expensive for "normal" use (medium to small applications), it just …
Chose Azure SQL Database
We looked at Google Cloud SQL and Amazon RDS services, but we did not want to switch to a different structure from the system we currently use.
Chose Azure SQL Database
It is very easy to setup SQL database on Azure. one can always refer to their documentation for best practices. It is highly available and scalable. It is cheaper than its alternatives and provide better performance than others. As we are using many other services of Azure for …
Chose Azure SQL Database
Amazon RDS for SQL Server is the best example to compare with Azure SQL Database since both provide a Microsoft SQL Engine to host your databases.

Amazon RDS for SQL is much more compatible with your on-premises databases than Azure SQL, the reason is that Amazon RDS for SQL …
Chose Azure SQL Database
The Azure SQL Database, compared to our on premise SQL server installation, is much easier to use in terms of seeing database diagnostics. There is a whole visualization platform that comes with the tool that will allow your database administrator to see what jobs are tying up …
Chose Azure SQL Database
Amazon's RDS offering is actually very good and is used in other parts of the company, we just have a lot of Azure experience so wanted to leverage that.
Chose Azure SQL Database
Azure SQL has a slight advantage over its rivals because it's developed by Microsoft, so it is well suited to professionals.
Chose Azure SQL Database
Being able to manage our databases in the cloud, scale quickly, and only require access to VMs made choosing Azure a no-brainer over a traditional SQL Server installation/integration. We don't have the budget or resources to integrate and maintain servers on our own, so using …
Chose Azure SQL Database
I would say MySQL in either Aurora or MariaDB form come close however, Azure SQL Database has a more streamlined approach to delivering a consistent programmability model, supported drivers and feature set.
Azure SQL Database T-SQL is advantageous and more complete than SQL …
Chose Azure SQL Database
Azure owned by Microsoft who owned SQL Server, so provided a variety of tools for easy migration/transition and from on-premises to the cloud; and management. I recommend using Azure for any on-prem SQL server databases.
Chose Azure SQL Database
Very similar product. Our company preferred to remain in the Microsoft Software Suite.
Chose Azure SQL Database
Azure SQL is a clear upgrade to SQL Server 2012 and pretty much has the advantage with all the extra features that it has. Security, queries, exporting tables, T-SQL has all improved. Transitioning 18+ years of an in-house database to the cloud was a struggle, but for the …
Chose Azure SQL Database
We moved away from Oracle and NoSQL because we had been so reliant on them for the last 25 years, the pricing was too much and we were looking for a way to cut the cord. Snowflake is just too up in the air, feels like it is soon to be just another line item to add to your Azure …
Chose Azure SQL Database
Amazon Relational Database Service is the other obvious competitor. We were already in Azure, so it's not a serious contender for our business due to that bias already, but I do personally find the marketing and documentation of RDS more intimidating to sort through.
Chose Azure SQL Database
Comparing with Amazon Aurora: Azure SQL DB is 100% compatible with SQL Server and Aurora is compatible with MySQL and PostGreSQL. Because of if, SQL DB suits large enterprises with hundreds of databases better.
Comparing with Oracle: the main issue is that Oracle will try to …
Chose Azure SQL Database
It reduces the business cost as it provides large storage capacity with massive speed. Data security is primary benefit which this product gives me.
Chose Azure SQL Database
It stacks up in different ways, for the most part, I think Microsoft is doing a really good job versus the competition. They basically started database type products from the beginning. I've always been excited about updates and can see their progress over time. Get's me really …
Features
PostgreSQLAzure SQL Database
Database-as-a-Service
Comparison of Database-as-a-Service features of Product A and Product B
PostgreSQL
-
Ratings
Azure SQL Database
7.3
Ratings
14% below category average
Automatic software patching00 Ratings6.30 Ratings
Database scalability00 Ratings7.80 Ratings
Automated backups00 Ratings7.80 Ratings
Database security provisions00 Ratings8.80 Ratings
Monitoring and metrics00 Ratings6.80 Ratings
Automatic host deployment00 Ratings6.10 Ratings
Best Alternatives
PostgreSQLAzure SQL Database
Small Businesses
InfluxDB
InfluxDB
Score 9.0 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Medium-sized Companies
SQLite
SQLite
Score 8.0 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
Enterprises
SQLite
SQLite
Score 8.0 out of 10
IBM Cloudant
IBM Cloudant
Score 7.4 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
PostgreSQLAzure SQL Database
Likelihood to Recommend
8.3
(0 ratings)
8.0
(0 ratings)
Likelihood to Renew
9.0
(0 ratings)
8.0
(0 ratings)
Usability
8.3
(0 ratings)
8.5
(0 ratings)
Availability
9.0
(0 ratings)
-
(0 ratings)
Performance
7.0
(0 ratings)
-
(0 ratings)
Support Rating
9.3
(0 ratings)
9.0
(0 ratings)
Implementation Rating
9.0
(0 ratings)
-
(0 ratings)
Product Scalability
8.0
(0 ratings)
-
(0 ratings)
User Testimonials
PostgreSQLAzure SQL Database
Likelihood to Recommend
Based on my experience, PostgreSQL is exactly what I imagine when thinking of a relational database: it is fast for querying and intuitive (if the underlying relations have been well written) and its writes are also efficient. Of course you need to know that a relational database is what you need, for example I would not recommend it if you have a lot of unstructured data that have no way to create a relation from and if you need to run heavy aggregations over your data, as it is not where PostgreSQL would shine.
Read full review
Your upcoming app can be built faster on a fully managed SQL database and can be moved into Azure with a few to no application code changes. Flexible and responsive server less computing and Hyperscale storage can cope with your changing requirements and one of the main benefits is the reduction in costs, which is noticeable.
Read full review
Pros
  • The stability it offers, its speed of response and its resource management is excellent even in complex database environments and with low-resource machines.
  • The large amount of resources it has in addition to the many own and third-party tools that are compatible that make productivity greatly increase.
  • The adaptability in various environments, whether distributed or not, [is a] complete set of configuration options which allows to greatly customize the work configuration according to the needs that are required.
  • The excellent handling of referential and transactional integrity, its internal security scheme, the ease with which we can create backups are some of the strengths that can be mentioned.
Read full review
  • Scalability is #1: if it used to be an almost no-win endeavour to try to modernize your server or migrate to other hardware, with Azure SQL Database it becomes a press of a button.
  • All the tools simply work after you are on Azure SQL Database.
  • The applications do not need changes in order to start using Azure SQL Database.
  • Hybrid Cloud scenarios will work.
  • Clustering and failover - already there.
  • You can start monitoring the use and extract performance insights in a new way in Azure.
Read full review
Cons
  • The query syntax for JSON fields is unwieldy when you start getting into complex queries with many joins.
  • I wish there was a distinction (a flag) you could set for automated scripts vs working in the psql CLI, which would provide an 'Are you sure you want to do X?' type prompt if your query is likely to affect more than a certain number of rows. Especially on updates/deletes. Setting the flag in the headless(scripted) flow would disable the prompt.
  • Better documentation around JSON and Array aggregation, with more examples of how the data is transformed.
Read full review
  • A little slow on processing complex or large Views. We use a lot of Views to feed our BI system, and the processing time could see some improvement, IMHO.
  • Additional monitoring components would be nice too, automating some built in performance measurement tools would be a nice feature.
  • Price can always be improved as well. It’s not bad, but room for improvement.
Read full review
Likelihood to Renew
As a needed software for day to day development activities
Read full review
This is best solution as a DBA one could expect from a service provider and as a cloud service, it removes all your hassles.
Read full review
Usability
Postgresql is the best tool out there for relational data so I have to give it a high rating when it comes to analytics, data availability and consistency, so on and so forth. SQL is also a relatively consistent language so when it comes to building new tables and loading data in from the OLTP database, there are enough tools where we can perform ETL on a scalable basis.
Read full review
The interfaces are intuitive once you are familiar with all the functions. The ability to use different tools to interact with the platform, such as directly via a browser or code editors such as VS Code or Visual Studio is a great option and allows for integrating withn the project and other testing and developing tools.
Read full review
Reliability and Availability
PostgreSQL's availability is top notch. Apart from connection time-out for an idle user, the database is super reliable.
Read full review
No answers on this topic
Performance
The data queries are relatively quick for a small to medium sized table. With complex joins, and a wide and deep table however, the performance of the query has room for improvement.
Read full review
No answers on this topic
Support Rating
There are several companies that you can contract for technical support, like EnterpriseDB or Percona, both first level in expertise and commitment to the software.
But we do not have contracts with them, we have done all the way from googling to forums, and never have a problem that we cannot resolve or pass around. And for dozens of projects and more than 15 years now.
Read full review
We give the support a high rating simply because every time we've had issues or questions, representatives were in contact with us quickly. Without fail, our issues/questions were handled in a timely matter. That kind of response is integral when client data integrity and availability is in question. There is also a wealth of documentation for resolving issues on your own.
Read full review
Online Training
The online training is request based. Had there been recorded videos available online for potential users to benefit from, I could have rated it higher. The online documentation however is very helpful. The online documentation PDF is downloadable and allows users to pace their own learning. With examples and code snippets, the documentation is great starting point.
Read full review
No answers on this topic
Implementation Rating
The online documentation of the PostgreSQL product is elaborate and takes users step by step.
Read full review
No answers on this topic
Alternatives Considered
In my experience using all of these products over many years, PostgreSQL is better than any of them in reliability, performance, productivity, cost, scalability and interoperability across operating systems.
Read full review
I selected Azure SQL because it integrates nicely with the technology stacks we currently maintain. The pricing is right, and clients are happy with that. Scaling is easy. Most of our clients don't want to maintain a full-blown database server, and they don't need one. For them, Azure SQL is the right size.
Read full review
Scalability
The DB is reliable, scalable, easy to use and resolves most DB needs
Read full review
No answers on this topic
Return on Investment
  • A robust and reliable platform reduces the risk of data loss and confusion.
  • Using an almost free product is economical. No license fees = minimal ownership cost.
  • Efficiency is high due to quickness and excellent resource management.
  • PostgreSQL helps us achieve our goals, and there are no time-consuming management tasks.
Read full review
  • Positive: very easy implementation!
  • Positive: finally a good (easy) implementation of data masking, something we always neglected on premise.
  • Positive: no maintenance!! No "server is down" messages on your phone at 3 'o clock in the morning.
  • Negative: Too expensive to use for all other scenario's than a few very important applications.
Read full review
ScreenShots