No more typing reviews! Try our Samantha, our new voice AI agent.

Google Cloud Spanner vs Microsoft Azure SQL Database comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Aug 12, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Google Cloud Spanner
Ranking in Database as a Service (DBaaS)
8th
Average Rating
9.2
Reviews Sentiment
7.8
Number of Reviews
5
Ranking in other categories
No ranking in other categories
Microsoft Azure SQL Database
Ranking in Database as a Service (DBaaS)
1st
Average Rating
8.6
Reviews Sentiment
6.9
Number of Reviews
134
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the Database as a Service (DBaaS) category, the mindshare of Google Cloud Spanner is 7.3%, up from 5.1% compared to the previous year. The mindshare of Microsoft Azure SQL Database is 9.2%, down from 14.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Database as a Service (DBaaS) Mindshare Distribution
ProductMindshare (%)
Microsoft Azure SQL Database9.2%
Google Cloud Spanner7.3%
Other83.5%
Database as a Service (DBaaS)
 

Featured Reviews

Ethan Lo - PeerSpot reviewer
Infrastructuer Security at Premise Data
A stable and scalable relational database that ensures a return on investment for its users
The most valuable feature of the solution is its scalability. Scalability comes with two options, among which Google Cloud Spanner can scale horizontally, compared to other relational databases that scale vertically. You can change Google Cloud Spanner's resource configuration, which is done through processing units. Suppose you set up Google Cloud Spanner initially with a hundred processing units, and then you run out of resources since your database used too much CPU. In the aforementioned scenario, you can scale up or down and face no downtime in the production phase. The solution's features are important when running a company twenty-four hours, seven days a week.
Thomas Sawyer - PeerSpot reviewer
Executive Director, Platform Architecture at Sumitomo Mitsui Banking Corporation – SMBC Group
Automatic tuning and multi-region availability have reduced manual workloads and improved performance management
The features of Microsoft Azure SQL Database that I like the most are easy scaling and high availability. I appreciate those features because it's easy to make Microsoft Azure SQL Database readily available in a multi-region infrastructure. Using Microsoft Azure SQL Database is very easy; it's much easier than SQL on-premise because I don't have to worry about deploying infrastructure, and I can rapidly deploy via infrastructure as code. I am using the automatic tuning feature in Microsoft Azure SQL Database. We are using the new feature of data encryption in Microsoft Azure SQL Database with customer-managed keys only. The reliability and stability of Microsoft Azure SQL Database platform are rock-solid; it's as good, if not better, than what our on-premise stability has been from an uptime perspective.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The application deployment in the cloud is the best feature of the infrastructure."
"Google Cloud Spanner is stable."
"It is a very scalable solution."
"The solution is stable and reliable."
"We can scale the solution if we need to."
"The most valuable feature of the solution is its scalability. Scalability comes with two options, among which Google Cloud Spanner can scale horizontally, compared to other relational databases that scale vertically."
"Microsoft technical support is good."
"The solution is very stable."
"We primarily and generally use it only for DB purposes. When it comes to the Azure part, we can easily provision, scale up, and scale down the generator machine. This kind of flexibility is the USP of SQL Azure. Its interface and ease of use are also valuable. It is very easy to use and integrate with multiple databases. If I need to pull in or import some data from my on-premises database, the ease with which you can connect and pull the data, not only from SQL Server but also from other flavors of MySQL or even Oracle, is very good."
"The backup features are the most valuable."
"I'd give Microsoft Azure SQL Database a nine out of ten."
"It is a good product for any new development or organization."
"The stability is excellent because it is easier for us to connect to the cloud rather than connecting to MSSP."
"The main advantage of it is that there is no infrastructure cost; we don't have to host it here, and we can grow it or shrink it depending on the demand with no restraint on capacity."
 

Cons

"I want to improve the deployment of cameras and surveillance infrastructure."
"The cost can be a bit high."
"The tool lacks to offer AI features."
"Google came up with something called Cloud Spanner Emulator, which fails to work like the real product if I want to develop some code and run a database locally on my machine."
"The tool needs to improve horizontal scaling."
"Some data types are not available on SQL Azure while it's available on SQL Server."
"Scalability Cost efficiency Business continuity"
"Microsoft could improve its documentation and support."
"I'm not really a SQL DBA, so I can't go into the depths of the areas that need to be improved. They can maybe make it a bit easier to educate people on how to develop SQL Server in Azure. They can provide some free seminars and webinars and more training in general for easier migration. I know there is some stuff on Microsoft learning, but it would be helpful and useful to have more up-to-date content."
"Its automation can be improved. SQL Server Agent was a very big part of the on-prem tools. While moving from on-prem to the cloud, redoing some of such tools was very cumbersome in Azure. There was a whole new set of technologies and methodologies. It should have easier automation-type features to be able to implement such tools. It should have almost a SQL agent type of substance built into that."
"The latency and availability of Microsoft Azure SQL Database can be problematic when connecting to an instance in a geographically distant location."
"Some issues with scalability."
"One area for improvement could be expanding the search queries using vectors or AI inside the database. After seeing its potential in a workshop, I realized the usefulness of more advanced search queries with AI."
 

Pricing and Cost Advice

"Price-wise, I heard that Google Cloud Spanner is on the higher side."
"The solution is expensive."
"It is expensive."
"Google Cloud Spanner is an expensive solution."
"SQL Azure is an expensive solution."
"Compared to other providers, the pricing is definitely on the affordable side."
"It only has a subscription-based license."
"I find that they are relatively expensive, especially when compared to AWS, where the prices are notably lower."
"We have had some issues with the licensing of the solution."
"From a licensing benefit standpoint, we have clients who are coming with their own SQL licensing with Software Assurance, and they are able to use those licenses for their Azure SQL and reduce costs."
"When you go with SQL Azure Database, you can create a small database, which is around $4 to $5 per month for development purposes."
"The licensing for this solution is based on subscription."
report
Use our free recommendation engine to learn which Database as a Service (DBaaS) solutions are best for your needs.
907,816 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
25%
Healthcare Company
9%
Computer Software Company
8%
Manufacturing Company
8%
Financial Services Firm
13%
Outsourcing Company
12%
Construction Company
10%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business60
Midsize Enterprise17
Large Enterprise61
 

Questions from the Community

What is your primary use case for Google Cloud Spanner?
Google Cloud Spanner has all the features of a traditional relational database, including schemas, SQL queries, ACID transactions, and provides excellent integration and monitoring tools as well as...
What is your experience regarding pricing and costs for Google Cloud Spanner?
Price-wise, I heard that Google Cloud Spanner is on the higher side. I am not sure if this is a rumor or if it's fake news, but I believe that having BigQuery and GCP together could be a little cos...
What needs improvement with Google Cloud Spanner?
The tool lacks to offer AI features. In the future, I would like the product to offer AI features to users. Nowadays, we are creating small acronyms for our SQL Server. We put some templates. If I ...
What is your experience regarding pricing and costs for SQL Azure?
I would say I am at a basic experience level with the pricing, setup costs and licensing because while I am the administrator for the service, I do not provision the services and worry about the co...
What needs improvement with SQL Azure?
I have no comments at the moment on how Microsoft Azure SQL Database can be improved. I have no comments on additional features that I would like to see released in the next release. I do not have ...
What is your primary use case for SQL Azure?
My main use cases for Microsoft Azure SQL Database are third-party applications.
 

Also Known As

Google Spanner
No data available
 

Overview

 

Sample Customers

Streak, Optiva, Mixpanel
adnymics GmbH, LG CNS, Centrebet, netfabb GmbH, MedPlast, Accelera Solutions, Sochi Organizing Committee, realzeit GmbH
Find out what your peers are saying about Google Cloud Spanner vs. Microsoft Azure SQL Database and other solutions. Updated: August 2026.
907,816 professionals have used our research since 2012.