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

"It is a very scalable solution."
"We can scale the solution if we need to."
"Google Cloud Spanner is stable."
"The application deployment in the cloud is the best feature of the infrastructure."
"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."
"The solution is stable and reliable."
"SQL Server's ability to automate data processing and validation through virtual agents and integration with other Microsoft applications like Power Virtual Agents and Azure SQL has dramatically improved efficiency."
"It is easy to scale in Azure in a way that I cannot scale on-prem."
"I don't think Oracle has any capabilities that SQL Azure lacks, and it's not used in as many companies and institutions."
"The compatibility with SQL Server for transitioning legacy systems to Microsoft Azure SQL Database is very important because it gives us assurance that what we experience today, we can get the same performance on the other side."
"Transitioning from a traditional on-premise SQL database to Microsoft Azure SQL Database is beneficial because features such as auto-indexing allow us to scale during peak seasons and scale back on demand, which is very useful for handling our spiky peak traffic based on seasonal factors, avoiding the need to purchase more hardware as required with traditional setups."
"Microsoft Azure SQL Database has significantly reduced our total cost of ownership by eliminating the need for a dedicated environment to host SQL."
"Customers can benefit from a lot of cost savings if they go for Azure."
"The initial setup is very straightforward; it's not complex at all, and for us, it did not take more than one or two hours, so it was quick to deploy."
 

Cons

"I want to improve the deployment of cameras and surveillance infrastructure."
"The tool needs to improve horizontal scaling."
"The tool lacks to offer AI features."
"The cost can be a bit high."
"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."
"They can maybe make it a bit easier to educate people on how to develop SQL Server in Azure."
"Microsoft Azure SQL Database is one of those solutions that helps consolidate our infrastructure, though unfortunately it is not the only solution we use."
"The default 1433 port for communication should be customizable because most hacks or attacks are attempted when creating any application or database on the default port."
"The reason for this rating is that we do not get the support we need unless it is a critical situation. For example, in a priority B case, the support engineer may not contact us for two days, which is a significant area for improvement."
"They should include more accessible functions for image tooling."
"There is so much information that it becomes confusing at times. The information can be more friendly. They could also provide additional training, especially at the beginning."
"It would help if the solution was more secure."
"The pricing plans when using multiple Microsoft solutions are complex and have room for improvement."
 

Pricing and Cost Advice

"It is expensive."
"Google Cloud Spanner is an expensive solution."
"Price-wise, I heard that Google Cloud Spanner is on the higher side."
"The solution is expensive."
"I would like it to be cheaper, but comparatively, it is reasonably priced."
"I would rate the pricing a seven out of ten."
"When looking at the long-term expenses associated with running software on an on-premises server, the costs are almost equivalent but when we include insurance for devices, onsite fees for servers, and other related costs, we may find that this is a cost-effective solution."
"The licensing for this solution is based on subscription."
"It is expensive. Snowflake and PostgreSQL are cheaper than this. Google is also cheaper than Azure. Its licensing is on a pay-as-you-go basis. It is based on usage and storage."
"SQL Azure's licensing cost is expensive."
"I recommend considering a pay-as-you-go pricing model initially."
"I am not aware of the exact pricing, but our monthly bill for Azure is around 80,000. It is less expensive than using SQL Server. It has the pay-as-you-go model, and the charges are based on the usage."
report
Use our free recommendation engine to learn which Database as a Service (DBaaS) solutions are best for your needs.
908,834 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.
908,834 professionals have used our research since 2012.