I'm currently involved in setting up pipelines on Azure for data extraction from a source to a target destination within specific time intervals. The goal is to automate the process of moving data efficiently.
Senior Consultant at a tech services company with 51-200 employees
A secure cloud-based relational database solution providing high availability and seamless integration into Azure services
Pros and Cons
- "One of the most valuable aspects is its seamless integration with Azure Data Factory."
- "There is room for improvement regarding the pricing structure."
What is our primary use case?
How has it helped my organization?
Previously, the database was on-premises, but now, with the SQL database in the Azure cloud, extracting information from on-premises automatically makes it available in the Azure cloud. The data becomes instantly accessible in the cloud, making it more efficient for you to work with. It's a straightforward and easy process.
What is most valuable?
One of the most valuable aspects is its seamless integration with Azure Data Factory. Its value lies in the significant time savings as there's minimal competition or customization challenges. This smooth integration makes it easy for me to work with both seamlessly.
What needs improvement?
There is room for improvement regarding the pricing structure. It would be beneficial if the cost is reduced.
Buyer's Guide
Microsoft Azure SQL Database
January 2026
Learn what your peers think about Microsoft Azure SQL Database. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
881,082 professionals have used our research since 2012.
For how long have I used the solution?
I have been working with it for more than a year.
What do I think about the stability of the solution?
The system is impressively reliable and stable. I would rate it ten out of ten.
What do I think about the scalability of the solution?
I would rate the scalability capabilities eight out of ten.
How are customer service and support?
I've had a positive experience working with their technical support team. I would rate it nine out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I currently use the Sophos server management solution, which is an on-premises solution. The primary reason for switching to SQL Azure is our plan to migrate to cloud.
How was the initial setup?
The initial setup used to be a bit complex, but now it's much easier. I would rate it eight out of ten.
What about the implementation team?
The deployment process is remarkably quick, taking only a few minutes to connect to the cloud and set up data storage. There's a standard setup without the need for additional or advanced deployment tools. It is handled by a dedicated team, constituting around three to five percent of the overall process. This includes individuals responsible for deployment, validation, and user support, ensuring a straightforward and efficient deployment experience.
What was our ROI?
The return on investment is a significant advantage for our company, especially since we've implemented this product across multiple distributions and clients. The satisfaction of our clients with the product support is notable. I would rate it nine out of ten.
What's my experience with pricing, setup cost, and licensing?
I find that they are relatively expensive, especially when compared to AWS, where the prices are notably lower.
What other advice do I have?
I would highly recommend it. Overall, I would rate it nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Product Architect at a tech vendor with 10,001+ employees
Has great scalability and simple management of the infrastructure
Pros and Cons
- "The scalability and simple management of the infrastructure are the most valuable features."
- "The problem is the automated configuration."
What is our primary use case?
The solution is used for a lender's business application.
What is most valuable?
The scalability and simple management of the infrastructure are the most valuable features.
What needs improvement?
They have some problems with the introduced features in the latest version of the server. The multiple query planning parameters have problems. The problem is the automated configuration. Even when they address the problems, there are still issues.
The second issue is to audit the real users on behalf of whom we operate secret servers. Normally in our application, we use only a single connection to leverage the pooling.
For how long have I used the solution?
I have been working with SQL Azure for eight years.
What do I think about the stability of the solution?
The solution is highly stable. I rate the stability a ten out of ten.
What do I think about the scalability of the solution?
The solution is hugely scalable yet it does not support auto-scaling and it is very time-consuming. The PR database takes a lot of time hence one should keep another server synchronized with the dataset. Presently, ninety thousand users are using the solution. I rate the scalability a six out of ten.
How are customer service and support?
The technical support is very good.
How was the initial setup?
The initial setup is very straightforward.
What's my experience with pricing, setup cost, and licensing?
I would rate the pricing a seven out of ten.
What other advice do I have?
I would rate the overall solution a nine out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Buyer's Guide
Microsoft Azure SQL Database
January 2026
Learn what your peers think about Microsoft Azure SQL Database. Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
881,082 professionals have used our research since 2012.
Senior Consultant at a tech services company with 201-500 employees
Good stability with a straightforward deployment
Pros and Cons
- "The preset configuration switches we can select on SQL Azure should be made more liberal to work on."
What is our primary use case?
We usually work on a valuation basis. When a customer wants to get on to our cloud, we suggest SQL Azure to them.
What needs improvement?
The preset configuration switches we can select on SQL Azure should be made more liberal to work on. The licensing cost for the solution is very expensive and should be improved.
For how long have I used the solution?
I have been using SQL Azure for eight years.
What do I think about the stability of the solution?
SQL Azure is a stable solution.
What do I think about the scalability of the solution?
SQL Azure is a scalable solution. Around 30 to 40 customers are using the solution.
How are customer service and support?
Their customer support is not ok at all because sometimes the tickets we raise don't get authorized.
How was the initial setup?
The initial setup for the solution is easy. It takes around 10 to 15 minutes to set up the solution. The deployment of the solution is straightforward.
What was our ROI?
The ROI depends on the customer and the scenario.
What's my experience with pricing, setup cost, and licensing?
SQL Azure's licensing cost is expensive.
What other advice do I have?
SQL Azure is a cloud-based solution. We usually require one or two people to deploy and maintain the solution. I would recommend SQL Azure for other people who don’t want to manage their environment. The worst thing about Microsoft is that it has a very bad license agreement that nobody understands.
Overall, I rate SQL Azure an eight out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
DB and Systems Engineer at a financial services firm with 51-200 employees
Stable, scalable, and good support
Pros and Cons
- "SQL Azure is reliable and scales well."
- "The solution could improve by allowing the export of the data more seamlessly. It is difficult to copy and back up data."
What is our primary use case?
We are using SQL Azure for databases that are hosted in Microsoft Azure.
What is most valuable?
SQL Azure is reliable and scales well.
What needs improvement?
The solution could improve by allowing the export of the data more seamlessly. It is difficult to copy and back up data.
For how long have I used the solution?
I have been using SQL Azure for three years.
What do I think about the stability of the solution?
I rate the stability of SQL Azure an eight out of ten.
What do I think about the scalability of the solution?
We have approximately 1,000 people using the solution in my organization.
I rate the scalability of SQL Azure a nine out of ten.
How are customer service and support?
The support is good.
How was the initial setup?
I rate the initial setup of SQL Azure a nine out of ten.
What's my experience with pricing, setup cost, and licensing?
The solution is expensive.
What other advice do I have?
I rate SQL Azure a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Consultant at a consultancy with 11-50 employees
Stable and scalable solution; could improve integrations with business intelligence software
Pros and Cons
- "My impression is that this solution is quite stable."
- "I think this product can improve its integrations with business intelligence software. The integrations are always cumbersome due to the approvals, passwords, et cetera."
What needs improvement?
I think this product can improve its integrations with business intelligence software. The integrations are always cumbersome due to the approvals, passwords, et cetera.
For how long have I used the solution?
I have been using this solution for the last three years.
What do I think about the stability of the solution?
My impression is that this solution is quite stable. I would rate its stability an eight, on a scale from one to 10, with one being the worst and 10 being the best.
What do I think about the scalability of the solution?
I would rate the scalability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best. Currently, there are two users of this solution in our company.
What about the implementation team?
I will be doing the implementation myself with the help of a third party.
Which other solutions did I evaluate?
We evaluated the SQL Server in addition to this solution, but we ultimately chose Azure mainly to have everything on one platform.
What other advice do I have?
Overall, I would rate this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Technical advisor and software architect at a educational organization with 201-500 employees
Stores complex relational data with consistency requirements and handles query tuning and security very well
Pros and Cons
- "I prefer using Microsoft SQL Server because I like the experience and the way Microsoft handles the query tuning and security."
- "One of the nice features in Microsoft SQL Server is the SQL Server CLR, which we sometimes need to use to protect our procedures using C# or CLR. This is not available in the SQL Azure database."
What is our primary use case?
We use SQL Azure to store our relational data. Whenever I have complex relational data with consistency requirements, I use SQL Azure Database.
I'm currently working in a small startup. There are just two people using this solution now: a developer and myself. I'm working as a technical consultant and an architect.
What is most valuable?
Microsoft recently added a JSON feature. I use all the features in a normal relational database, and they're very helpful. I prefer using Microsoft SQL Server because I like the experience and the way Microsoft handles the query tuning and security. These are really good features for database experts.
What needs improvement?
One of the nice features in Microsoft SQL Server is the SQL Server CLR, which we sometimes need to protect our procedures using C# or CLR. This feature isn't available in the SQL Azure database. It's available in the Managed Instance in the Azure Database.
You can create SOAR procedures using C# and can get user-defined functions using C#. You can extend the database and the data files using CLR files. This feature isn't available on the Microsoft Azure SQL Database. I understand they can't add it because it's a managed service, and having CLR probably doesn't work for them, but it would be nice if they could add this feature.
For how long have I used the solution?
I have used this solution for almost six years.
What do I think about the stability of the solution?
I would rate the stability as eight out of ten.
What do I think about the scalability of the solution?
It is very scalable, depending on how much you're willing to pay. We can have up to 4,000 DTUs, but we haven't needed that much scalability.
How are customer service and support?
We had an instance where we weren't able to deploy Cosmos DB on a UAE data center, and Microsoft helped us. We haven't had any issues so far with technical support.
How was the initial setup?
Setup is straightforward. You just create an SQL Server instance account on Azure, and then you can create SQL databases. It's very easy to create tables and procedures. I mainly use the SQL data buckets inside Visual Studio. From there, I deploy databases to Azure from Visual Studio.
What about the implementation team?
It's easy to do the deployment in-house. Visual Studio provides a lot of functionality to make deploying solutions to Azure simple and easy.
What was our ROI?
Using SQL Server database with all the features will provide a good return on investment. Once you move to Azure, you remove all the capital expenses by having to acquire the license and deploy it on-premises.
What's my experience with pricing, setup cost, and licensing?
When you go with SQL Azure Database, you can create a small database, which is around $4 to $5 per month for development purposes. It's very cheap in that respect. I think it's a little bit expensive compared to other services that Microsoft offers on Azure. PostgreSQL, MySQL, and MariaDB are a bit cheaper than SQL Server.
If the price were lower, I think it would become more attractive for developers to use.
What other advice do I have?
I would rate this solution as eight out of ten.
It's a very easy solution. Microsoft also has Data Explore. The entire Microsoft environment makes things easy for developers. It's very easy to set up SQL on Azure. I highly recommend it. I really like it, and I've been working with SQL Server since 2000.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Technical Lead at a tech services company with 10,001+ employees
Reliable with good security privileges and good templates
Pros and Cons
- "The product is easy to set up."
- "It does take some time to learn about the environment."
What is our primary use case?
This is one of the applications where we are supporting in production.
If we are using SQL STL, it is a manual process. If we use STL Azure, we will import all the templates from the Azure cloud or Microsoft cloud. There are already pre-defined templates and pre-defined procedures in Azure. We will be using those instead of manual processes. Azure is helping us to be more flexible and handle time scaling.
What is most valuable?
I have limited experience with the tool. It's hard to describe its best feature.
It's pretty helpful from a technical standpoint. It's also dominating other clouds, including AWS and Google. It's better at improving itself.
The product is easy to set up.
It's stable and reliable.
I find the product to be scalable.
The solution is pretty affordable.
Microsoft has a lot of useful security privileges.
What needs improvement?
I haven't really come across any shortcomings. I also have limited experience. We need to do more training and research.
It does take some time to learn about the environment.
For how long have I used the solution?
I've been using the solution for six months.
What do I think about the stability of the solution?
The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
The solution is easy to scale.
We have more than 1,000 people using the solution. I'm not sure of the exact number of users. We have multiple accounts and end customers.
How are customer service and support?
In terms of technical support, we do have a lot of subscription privileges. We do have seniors, and tech leads to assist. They can discuss issues with the vendor and technical support.
Which solution did I use previously and why did I switch?
We have used different solutions in the past. We found that if we worked manually, we would need more resources. With this solution, we have more time flexibility and stability. More complex things can be worked around.
How was the initial setup?
The initial setup is straightforward.
It is easy. We only use one account, a Microsoft Azure account, and we can pull all templates from there. It's got an easy user interface and admin interface which makes implementation straightforward. All you have to do is deploy all the scenarios. After that, it will take some time and flexibility to understand the environment.
It takes six hours to finish all the setup, including completing the installation of SQL and integrating with Genesis.
What's my experience with pricing, setup cost, and licensing?
We find the solution to be less expensive than other options.
What other advice do I have?
We're customers and end-users.
I would recommend this solution. Microsoft is very efficient and forward-looking - making it less expensive to build the setup for Azure SQL. Even though we do have one Microsoft account, we can directly integrate it with everything at one time. We do have limited licenses which makes it less expensive compared to the Google cloud or AWS or whatever else is in the other market.
I'd rate the solution eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Vice President (Technology) at a computer software company with 51-200 employees
Around-the-clock access to your database, maintenance-free, and good performance
Pros and Cons
- "The most valuable feature from the infra point of view is you don't have to keep any on-prem infrastructure, it is available all the time whenever you want to access it."
- "The solution can be improved by reducing the cost so more users can be added."
What is our primary use case?
Our primary use case of this solution is to host our databases and it is fulfilling our requirements.
What is most valuable?
The most valuable feature from the infra point of view is you don't have to keep any on-prem infrastructure, it is available all the time whenever you want to access it.
What needs improvement?
The solution can be improved by reducing the cost so more users can be added.
For how long have I used the solution?
I have been using the solution for 15 months.
What do I think about the stability of the solution?
Our customers work in the space of small and medium businesses area segment. For them, the way the solution is being offered and used is working and is considered to be stable.
What do I think about the scalability of the solution?
Not much is required in terms of scalability. So the foreign enterprises which are spanning the globe that requires scalability could be different. Small and medium businesses have a presence only in one location or maybe a couple of cities within a country. this is a reasonably scalable solution for them.
What's my experience with pricing, setup cost, and licensing?
The license is based on the number of users.
What other advice do I have?
I give the solution nine out of ten.
Currently, we have 25 to 30 developers using the solution.
There are alternative solutions available like Oracle or MySQL but I have not used any of them.
I recommend the solution.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Download our free Microsoft Azure SQL Database Report and get advice and tips from experienced pros
sharing their opinions.
Updated: January 2026
Product Categories
Database as a Service (DBaaS)Popular Comparisons
Microsoft Azure Cosmos DB
MongoDB Atlas
SingleStore
Google Cloud SQL
Oracle Database as a Service
Google Cloud Spanner
Azure Database for PostgreSQL
Oracle Exadata Cloud at Customer
Oracle Exadata Express Cloud Service
Couchbase Capella
Yugabyte Platform
IBM Db2 on Cloud
Yugabyte Cloud
Buyer's Guide
Download our free Microsoft Azure SQL Database Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- When evaluating Database as a Service, what aspect do you think is the most important to look for?
- What would be the best application SQL optimizer over the WAN?
- Which database is the best for session cashing?
- What is the biggest difference between Google BigQuery and Oracle Database as Service?
- Which low-code (no-code) database solution do you prefer?
- Which databases are supported under DBaaS solutions?
- Why is Database as a Service important for companies?


















