I am a system integrator using Microsoft Azure SQL Database for my customers. The major use case for Microsoft Azure SQL Database is that most of my clients have a lot of applications, so they are using SQL as a database.
Business Unit Head at UBG
Cloud database has reduced operational costs and supports flexible hybrid deployments
Pros and Cons
- "I see value for money and ROI with Microsoft Azure SQL Database because any solution requires manpower resources."
- "I do not like customer service from Microsoft; it is very bad. Their response is very poor; it takes too much time to reach the right engineer who can actually solve issues, and the internal process is too long."
What is our primary use case?
How has it helped my organization?
I speak about reduction in operational costs when using Microsoft Azure SQL Database. I have worked with Azure Hybrid Benefit, which does provide benefits on operations and helps to reduce costs because customers often need VMs or workloads temporarily. When we create a hybrid setup with temporary VMs on Azure connected to their on-premises environment, they only incur costs while using it.
Cloud database options are certainly important to my clients. The main reason cloud databases are important is that SQL performance issues often stem from the platform, such as Windows servers and certain patches causing connectivity issues. Using Azure as a service helps eliminate these dependencies on hardware.
What is most valuable?
As a system integrator, the biggest advantage of Microsoft Azure SQL Database is that I am primarily working within the Microsoft environment, and the enterprise feature I get is essential for replication, creating a DR, or a process of SQL. I am happy with Microsoft Azure SQL Database. That is the main reason people want to use it. Additionally, if I buy under the OVL or software assurance, I get direct support from Microsoft.
Integration with Microsoft applications regarding Microsoft Azure SQL Database is good; it is really awesome because both are in the Microsoft environment, making it really easy to integrate with SQL. In general, I find Microsoft Azure SQL Database easy to use.
On the security side, the security features of Microsoft Azure SQL Database are fine. Backup and restore are important functionalities because I cannot rely on one copy of data. I need multiple copies, which is why backup is required.
What needs improvement?
The automatic tuning feature in Microsoft Azure SQL Database impacts database performance sometimes. What happens with Microsoft Azure SQL Database's automatic tuning is that when SQL queries are executed, the automatic tuning creates some performance dump because the process behaves differently from what is expected, which is the main reason I disable this automatic tuning.
Regarding areas for improvement in Microsoft Azure SQL Database, since it is Windows-based, it has its pluses and minuses. Sometimes it behaves unexpectedly, and when I need to restart, I have to restart the entire server, not just the SQL service. I often face such issues.
Buyer's Guide
Microsoft Azure SQL Database
October 2026
Learn what your peers think about Microsoft Azure SQL Database. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
922,921 professionals have used our research since 2012.
For how long have I used the solution?
I started working with Microsoft Azure SQL Database almost three years ago or more. I do have experience with SQL database, so I started with Azure also.
What do I think about the stability of the solution?
I agree Microsoft Azure SQL Database is stable and reliable, with no significant glitches.
What do I think about the scalability of the solution?
Regarding scalability of Microsoft Azure SQL Database, it is easy to scale workloads. If I have dynamic requirements, there are no issues at all.
How are customer service and support?
I do not like customer service from Microsoft; it is very bad. Their response is very poor; it takes too much time to reach the right engineer who can actually solve issues, and the internal process is too long. If I had to rate Microsoft Azure SQL Database support subjectively, I would give them a six.
How was the initial setup?
Regarding installation, I think it is fine. All the open material is available, and I have not encountered any difficulties.
What was our ROI?
I believe that Microsoft Azure SQL Database helps to reduce Total Cost of Ownership (TCO) because people with long-term experience using Windows SQL are not buying any support. When using Azure, it is provided as a service, so they do not need extra support from Microsoft or anywhere. Most other databases like Oracle are very costly, and with open databases requiring 24/7 support, that also adds cost. I receive a better ROI on SQL databases.
I see value for money and ROI with Microsoft Azure SQL Database because any solution requires manpower resources. With Microsoft Azure SQL Database, any issue that arises can be resolved without depending solely on Microsoft or expert help. Combining license cost, operational cost, and manpower resources cost gives a better ROI.
What's my experience with pricing, setup cost, and licensing?
I think Microsoft Azure SQL Database is affordable, not expensive. Regarding migration, I am just keeping a professional service charge for that.
Which other solutions did I evaluate?
Regarding Microsoft Azure SQL Database compared to other solutions, I cannot say it is the most advanced. It is more about the user's knowledge. If I tune my database and know how to connect it with applications, it can compete with any database.
What other advice do I have?
Regarding the ability of Microsoft Azure SQL Database to power next-generation AI applications, I still have not done that. However, I am using OpenAI and other functionalities on Azure, but I do not know about AI integration with Microsoft Azure SQL Database. As for deployment, I use both on-cloud, on-premises, and hybrid environments. I would rate Microsoft Azure SQL Database a nine out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer. Integrator
Last updated: Oct 8, 2026
Flag as inappropriateProject Manager at Capgemini
Has enabled secure data access with seamless integration features while pricing remains a concern
Pros and Cons
- "Using Azure Active Directory is a great feature for securing our connectivity for any clients or users connecting to our data."
- "The only thing that concerns me today is the pricing connected with Microsoft Azure SQL Database; everything else is all right."
What is our primary use case?
Regarding Microsoft Azure SQL Database, I work with that product. For one of our projects, we need to use this Microsoft Azure SQL Database. We are using this Microsoft Azure SQL Database to store our data solution.
What is most valuable?
Azure Active Directory is something we are frequently using for our login to our application for the customer and for any application. Using Azure Active Directory is a great feature for securing our connectivity for any clients or users connecting to our data.
What needs improvement?
Regarding the transitioning option with SQL Server, using Microsoft Azure SQL Database is more costly than if we are using any other service because retrieving data and putting the throughput is a costlier part. Pricing is the only concern I see as a disadvantage for Microsoft Azure SQL Database. The only thing that concerns me today is the pricing connected with Microsoft Azure SQL Database; everything else is all right.
For how long have I used the solution?
Regarding Microsoft Azure SQL Database, I have worked with the product for around one year or a longer period of time.
What do I think about the stability of the solution?
Regarding the stability of Microsoft Azure SQL Database, it is stable.
What do I think about the scalability of the solution?
I find it easy to scale Microsoft Azure SQL Database.
How are customer service and support?
I would rate support for Microsoft Azure SQL Database as 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 have already used Oracle database earlier in my career, which is different from Microsoft.
How was the initial setup?
In terms of installation, it is not complicated, actually; it is quite simple.
What about the implementation team?
I purchased it from Azure only.
What's my experience with pricing, setup cost, and licensing?
The pricing for Microsoft Azure SQL Database is a bit high.
Which other solutions did I evaluate?
If we compare Microsoft Azure SQL Database to Oracle, the pricing would be different. Oracle products are less expensive if we compare them to Microsoft Azure SQL Database.
What other advice do I have?
I'm not using the Automatic Tuning feature directly. The biggest benefit from Microsoft Azure SQL Database is that we are choosing to use an Azure VM, where we are using our own database instead of using SQL Server; we have migrated from Microsoft Azure SQL Database to our internal SQL database. I don't think there are any features left to add to Microsoft Azure SQL Database; I see everything is there. All self-documentation is okay; I have no concerns about this. The review rating for Microsoft Azure SQL Database is 9 out of 10.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Buyer's Guide
Microsoft Azure SQL Database
October 2026
Learn what your peers think about Microsoft Azure SQL Database. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
922,921 professionals have used our research since 2012.
Senior Director at a tech vendor with 501-1,000 employees
Reduced our total cost of ownership because we don't have to spin up an environment just to contain SQL
Pros and Cons
- "Valuable features of Microsoft Azure SQL Database include its quick deployment capabilities, the ability to spin up an environment easily, and seamless integration with Microsoft products."
- "Microsoft Azure SQL Database has significantly reduced our total cost of ownership by eliminating the need for a dedicated environment to host SQL."
- "There needs to be a hybrid model for situations where not all customers want a cloud-based SQL solution."
- "The latency and availability of Microsoft Azure SQL Database can be problematic when connecting to an instance in a geographically distant location."
What is our primary use case?
Our primary use case for Microsoft Azure SQL Database is storage configuration. We store all our connector configurations in the database, ensuring seamless operational integration.
How has it helped my organization?
Microsoft Azure SQL Database is easy to use and allows for rapid deployment.
While integrating the AI app with Azure SQL Database is a consideration, it's more for configurations. I believe the next steps should involve exploring search indices and technologies like Fabric.
This solution has had a certain impact on our organization. It has reduced our total cost of ownership because we don't have to spin up an environment just to contain SQL. All our databases now run in Azure, eliminating the need for on-premises instances.
Microsoft SQL Server seamlessly integrates with other Microsoft applications and is the central repository for all our connector configurations.
Microsoft Azure SQL Database has significantly reduced our total cost of ownership by eliminating the need for a dedicated environment to host SQL. Migrating all databases to Azure and removing on-premises instances has resulted in approximately a 70 percent reduction in TCO.
What is most valuable?
Valuable features of Microsoft Azure SQL Database include its quick deployment capabilities, the ability to spin up an environment easily, and seamless integration with Microsoft products. The transition to Azure SQL has certainly reduced our organization's total cost of ownership as it negates the need for on-premises infrastructure. The recent announcement about Copilot spinning up and creating SQL tables and stored procedures indicates the continuous improvement and added value it brings.
What needs improvement?
There needs to be a hybrid model for situations where not all customers want a cloud-based SQL solution. This model would facilitate transitions from on-premises instances to cloud-based versions.
For how long have I used the solution?
I have been using Microsoft Azure SQL Database for about 15 years.
What do I think about the stability of the solution?
The overall stability is good as it functions smoothly for our organization's needs.
The latency and availability of Microsoft Azure SQL Database can be problematic when connecting to an instance in a geographically distant location. For example, connecting from New York to an instance in Australia can result in network issues. Therefore, it is preferable to provision an instance local to the connection point to optimize performance and minimize latency.
What do I think about the scalability of the solution?
Microsoft Azure SQL Database allows easy scaling up and across without the need for physical infrastructure adjustments.
Which solution did I use previously and why did I switch?
We did not switch from another solution because we are a Microsoft-oriented company and have seamlessly used Microsoft products for many years.
What was our ROI?
Azure SQL Database has helped reduce our total cost of ownership because we don't have to spin up an environment just to contain SQL.
What other advice do I have?
I would rate Microsoft Azure SQL Database as a solid eight out of ten due to the room left for improvement. Microsoft has potential areas for enhancement and always seeks growth.
The migration of our database to Microsoft Azure SQL proceeded smoothly without challenges. This strategic business decision to transition from on-premises to Azure SQL was proactively incorporated into our roadmap.
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 has a business relationship with this vendor other than being a customer. Partner
Development Partner & Manager, Cloud at a tech vendor with 10,001+ employees
Cloud migration has boosted partner sales and now needs stronger governance for AI features
Pros and Cons
- "High reliability and availability specifically help my partners and my organization because it's easier to recover if something goes wrong somewhere."
- "On a scale of one to 10, I would rate Microsoft Azure SQL Database overall as seven."
What is our primary use case?
My main use case for Microsoft Azure SQL Database is helping partners sell it and find use cases for it.
A quick specific example of a use case I have helped a partner with is a migration from SQL Server to the cloud.
I have more to add about my main use case and how I support partners: we try to find suitable services for them to build on.
How has it helped my organization?
Microsoft Azure SQL Database has impacted my organization positively because it makes it possible to sell Azure more and help our partners with it more.
I have seen some growth in sales, productivity, and customer satisfaction, with some in all of the areas. I don't have any specific numbers to give right now.
What is most valuable?
In my opinion, the best features Microsoft Azure SQL Database offers are high reliability and availability.
High reliability and availability specifically help my partners and my organization. It's easier to recover if something goes wrong somewhere. If you don't have your database in the cloud, it's only on one server somewhere, and if it goes down, your business goes down.
For how long have I used the solution?
I have been using Microsoft Azure SQL Database for one year and a half.
What other advice do I have?
On a scale of one to 10, I would rate Microsoft Azure SQL Database overall as seven.
Overall, it's great, and that is what influenced my rating. There's always room for improvement.
The governance and security of Microsoft Azure SQL Database's AI capabilities is an area that we need to investigate more.
The accuracy and reliability of output of Microsoft Azure SQL Database's AI capabilities is also an area that we need to investigate more.
My advice to others looking into using Microsoft Azure SQL Database is to find out about the AI capabilities. They are the future and the present-day top tier. That is also something that I need to personally look into more.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Distributor
Last updated: Nov 20, 2026
Flag as inappropriateSenior Technical Lead (Sharepoint) at a manufacturing company with 10,001+ employees
Integrates with other Microsoft applications very well
Pros and Cons
- "The tool set is familiar since I've used SQL Server on-premises for quite a few years."
- "I'd give Microsoft Azure SQL Database a nine out of ten."
- "Azure SQL had a bit of a learning curve to start, but it was fairly simple once I understood how to develop it. I was using PowerShell to connect to it, and I've never connected to online databases through Azure using PowerShell. Scripting the PowerShell connections could be simpler. The coding is familiar, but figuring out how to use it initially can be easier."
- "Azure SQL had a bit of a learning curve to start, but it was fairly simple once I understood how to develop it."
What is our primary use case?
I use Azure SQL for reporting on data that I've collected for administration purposes.
How has it helped my organization?
Azure SQL improves my personal productivity because I can have a larger database.
What is most valuable?
The toolset is familiar to me since I've used SQL Server on-premises for quite a few years. Azure SQL Server integrates with other Microsoft applications very well.
What needs improvement?
Azure SQL had a bit of a learning curve to start, but it was fairly simple once I understood how to develop it. I was using PowerShell to connect to it, and I've never connected to online databases through Azure using PowerShell. Scripting the PowerShell connections could be simpler. The coding is familiar, but figuring out how to use it initially can be easier.
For how long have I used the solution?
I have been using Azure SQL for about a year.
What do I think about the stability of the solution?
It seems like the stability is getting there.
What do I think about the scalability of the solution?
I have not seen any issues with scalability. My database is not huge, but it's not small. It handles it quite well and is pretty fast.
How are customer service and support?
I used some product documentation for PowerShell scripting. Other than that, I didn't reach out to support or any of our TAMs.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Familiarity was the reason for choosing SQL. I knew SQL, so that's what I preferred to do. SQL seemed to be the one with familiarity and price as key factors.
How was the initial setup?
Our environment has a lot of security, so we have to open channels and configure the prerequisites for connectivity. Before you start implementing, you need everything to be set up.
What other advice do I have?
I'd give Microsoft Azure SQL Database a 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.
Software Engineer at a financial services firm with 51-200 employees
Has greatly improved maintainability by eliminating the need to manage on-premises SQL servers
Pros and Cons
- "The ease of scaling the server up and down by simply pressing a few buttons in a dropdown menu has made our lives significantly more comfortable, especially as we aim to process more data this year by utilizing the cloud."
- "We've noticed an unexpected increase in the cost of running the server over the past few months."
What is our primary use case?
We use it primarily as a data warehouse. We receive a lot of data from external vendors, and our goal is to consolidate all the information. Using data from various sources, we generate reports to support internal teams in the organization, mainly for operational tasks.
How has it helped my organization?
Microsoft Azure SQL Database has greatly improved maintainability by eliminating the need to manage on-premises SQL servers. The ease of scaling the server up and down by simply pressing a few buttons in a dropdown menu has made our lives significantly more comfortable, especially as we aim to process more data this year by utilizing the cloud.
It has helped to reduce our organization's total cost of ownership when it comes to our IT team who don't spend as much money on hardware, cooling, monitoring temperatures, and tasks like that. I know that IT people don't have to come into the office on weekends to make upgrades, do maintenance, or if there are alerts, and tasks like that.
What is most valuable?
It is easy to use. We interface with it using SQL Server Management Studio, which only requires a change in connection, so the interface remains consistent. This simplicity in usability, along with improved organizational productivity where we no longer need to maintain on-premises SQL servers, is invaluable. Scaling up and down the server with ease is a significant benefit, particularly as we aim to handle an increased data workload this year. Additionally, the integration of multiple services within Azure simplifies our operations.
My company is in the early stages of exploring its ability to power next-generation AI applications. We've tried AI Studio. It's a little too data science-y for what our team does. Trying to connect our data with AI has a high learning curve.
It's been really easy to integrate with other Microsoft applications. We're currently in the middle of migrating a bunch of ETL packages and processes to Azure Data Factory. Everything living in Azure makes it really easy.
Maintainability has increased a lot. We don't have to maintain the on-prem SQL Server because we don't have to maintain anything anymore. Maintainability has increased a lot in terms of the amount of time needed to do that. It's been really nice being able to scale the server up and down. It's made our lives a lot easier, especially since we're trying to ingest much more data this year.
What needs improvement?
We're trying to manage our costs better. We've noticed an unexpected increase in the cost of running the server over the past few months. Addressing pricing clarity and alignment would help us. Also, incorporating AI functionalities like Copilot into SQL Server Management Studio could enhance productivity by assisting with query writing and troubleshooting.
For how long have I used the solution?
Professionally, I have been using SQL for about five years. At my company, we used on-premises databases for a long time, and in January of this year, we migrated to Microsoft Azure SQL Database. We have been running it for eleven months now.
What do I think about the stability of the solution?
So far, there have been no issues reported with latency and availability.
What do I think about the scalability of the solution?
The experience has been positive. It is easy to scale up when needed and scale back down if required.
Which solution did I use previously and why did I switch?
We used on-premises SQL servers. The switch to Microsoft Azure SQL Database was influenced by the elimination of maintenance required for on-premises systems and the desire to manage all technologies under one umbrella within Azure, considering our existing cloud footprint.
How was the initial setup?
The initial setup was straightforward. It involved changing the connection string within SQL Server Management Studio, maintaining consistency in interfacing.
The team that migrated struggled with replication in the very beginning where replicating our database for redundancy seemed like it was over replicating. The amount of storage that it was taking up was four to five x our actual database size. We had to increase the capacity of it and that increased cost for a little bit until we shut down the replication.
What's my experience with pricing, setup cost, and licensing?
The price for running the server increased more than expected in recent months, and better alignment of pricing expectations is needed. Notably, costs related to IT staff coming into the office on weekends or monitoring hardware have presumably decreased.
Which other solutions did I evaluate?
During our evaluation, pricing was a key consideration, and Microsoft Azure's pricing model was more appealing compared to other competitors. The extensive cloud footprint we already had in Azure contributed to our choice.
What other advice do I have?
On a scale from one to ten, I rate the overall product an eight.
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.
Specialist Datacenter and Server at IHS Towers
Enables seamless database provisioning and enhances security management for application teams
Pros and Cons
- "The database is extremely scalable, allowing seamless scaling up or down with a simple change in parameters."
- "Pricing could be improved to make Microsoft Azure SQL Database more accessible."
What is our primary use case?
I provision the database, perform all the necessary security checks, and then provide access to the application teams that will consume it.
What is most valuable?
Microsoft Azure SQL Database is effective for availability, scalability, and security. The Software as a Service model is more effective and easier to access in terms of security, as Azure provides security at the security layer, reducing the risk of breach. Autoscaling is fantastic, automatically scaling up or down depending on usage parameters set. The database's security features depend on the pricing tiers chosen.
What needs improvement?
Pricing could be improved to make Microsoft Azure SQL Database more accessible. A reduction in price might encourage more users and bring more profit. Instead of a 20% or 30% reduction immediately, a gradual reduction could attract more users.
For how long have I used the solution?
I have worked with Microsoft Azure SQL Database for approximately six years.
What was my experience with deployment of the solution?
I haven't encountered any downtime issues. Changing parameters automatically scales up or down the database without any interruptions.
What do I think about the stability of the solution?
I have never encountered any challenges regarding stability. The database is very stable and straightforward.
What do I think about the scalability of the solution?
The database is extremely scalable, allowing seamless scaling up or down with a simple change in parameters. It's a perfect ten out of ten in terms of scalability.
How are customer service and support?
During my years of experience, I've never encountered an issue with Microsoft Azure SQL Database that I couldn't resolve, so I haven't needed to contact customer support.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup is very easy, given that all parameters and requirements from the application units are in place.
What's my experience with pricing, setup cost, and licensing?
The pricing of Microsoft Azure SQL Database is not cheap, affecting user uptake. A gradual reduction in price could improve accessibility and user numbers, making it easier for users to adopt the solution.
Which other solutions did I evaluate?
I have previous experience with 3PAR and StoreOnce from HPE.
What other advice do I have?
I advise users to adopt Microsoft Azure SQL Database, as it simplifies life for users and applications. Applications can connect from anywhere, and it reduces headaches for administrators and infrastructure teams. The disaster recovery plan and backup features are easily enabled. The overall rating is nine out of ten, considering pricing concerns.
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?
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Solutions Architect at ITCON SERVICES, LLC
Integrations with Microsoft Power Virtual Agents have dramatically improved efficiency
Pros and Cons
- "The Power Virtual Agents help us go through documents and load data into SQL."
- "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."
- "The document storage is primarily relational, which is not ideally suited for SQL. If there were better integration with SharePoint for document handling in SQL, it would greatly benefit the organization. Moreover, the current on-premise limitations prevent direct file pulling, limiting certain capabilities."
What is our primary use case?
The primary use case is working for a government client that receives a lot of data and information from all the states. They process these documents using Azure and Power Virtual Agents to retrieve information and store it in Azure SQL. Previously, we used it for .NET applications, and some of our core applications involved SharePoint, which has an SQL back end. The solution has a broad range.
How has it helped my organization?
Due to the continuous influx of data, we chose Azure SQL for faster processing. SQL Server has significantly improved organizational operations. Previously, managers had to manually review and manage thousands of records weekly, which is a slow process.
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 has expedited the data processing and validation, allowing managers to focus on strategic tasks.
What is most valuable?
The Power Virtual Agents help us go through documents and load data into SQL.
The next stage is to create chatbots for customers to send us information. This automation has been a fantastic improvement over previous manual processes
What needs improvement?
The document storage is primarily relational, which is not ideally suited for SQL. If there were better integration with SharePoint for document handling in SQL, it would greatly benefit the organization. Moreover, the current on-premise limitations prevent direct file pulling, limiting certain capabilities.
For how long have I used the solution?
We have used Azure SQL for around four years.
What do I think about the scalability of the solution?
One reason we chose Azure SQL was its scalability. We started with a few gigabytes of data, but we anticipate growth once we integrate chatbots and AI features, making Azure's scalability features like Elasticity essential.
How are customer service and support?
We had a positive experience with Microsoft support during implementation.
How would you rate customer service and support?
Positive
How was the initial setup?
The installation was smooth. We faced a few minor challenges on the government level with opening the firewalls for SQL to communicate with our applications. The cloud implementation is straightforward.
What about the implementation team?
The Microsoft FastTrack team played an integral role in the implementation, providing valuable guidance and expertise.
Which other solutions did I evaluate?
Data from SQL was previously pulled for different applications built on Java by creating APIs. We also prefer SQL because we have existing enterprise licenses with the government.
What other advice do I have?
I would rate Microsoft Azure SQL Database nine out of 10.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
CIO at a financial services firm with 1,001-5,000 employees
Native connection and efficiency in scaling workloads are quite beneficial
Pros and Cons
- "The initial setup was straightforward. We did not migrate from an existing system but implemented it from scratch and did not require Microsoft support. We were building Power Platform apps using SharePoint databases and Excel. And after that, we realized that we had to integrate it with SQL. It wasn't too hard, and our partners have people with experience."
- "Azure SQL connects directly to our Power Platform apps, making it easy to use."
- "A potential area for improvement could be integrating with third-party clouds. Adding a feature to bring Azure SQL in Azure with SQL on-premises would be helpful."
What is our primary use case?
Our primary use case is for Power Platform apps.
How has it helped my organization?
Azure SQL doesn't require any maintenance because Azure handles all that. is handled in Azure. Our team can focus on other activities instead of database management, and we save around two to three days a month.
What is most valuable?
Azure SQL connects directly to our Power Platform apps, making it easy to use. The integration with AI apps will be good because all the Azure AI apps are in the cloud, making it seamless. You don't need to connect to any on-premises or external sources to address integration. It will also speed up our data processing.
SQL's native connection and efficiency in scaling workloads are quite beneficial, and the ability to integrate well with other Microsoft applications adds significant value.
What needs improvement?
A potential area for improvement could be integrating with third-party clouds. Adding a feature to bring Azure SQL in Azure with SQL on-premises would be helpful.
For how long have I used the solution?
I have used Azure SQL for three to four years.
What do I think about the stability of the solution?
We haven't noticed any latency since we do not have mission-critical solutions on the cloud yet, and the stability has been good so far.
What do I think about the scalability of the solution?
If more space is needed in a specific moment of time, Azure SQL can grow and downsize quickly, demonstrating good scalability.
How are customer service and support?
I have found Microsoft's resources and support particularly helpful as they provide a big environment to work with.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup was straightforward. We did not migrate from an existing system but implemented it from scratch and did not require Microsoft support. We were building Power Platform apps using SharePoint databases and Excel. And after that, we realized that we had to integrate it with SQL. It wasn't too hard, and our partners have people with experience.
What about the implementation team?
We did the implementation ourselves without involving Microsoft support.
What was our ROI?
While I think there has been a reduction in our total cost of ownership, I have not measured it.
Which other solutions did I evaluate?
We did not evaluate other cloud databases as we preferred to maintain a standardized SQL environment.
What other advice do I have?
I rate Microsoft Azure SQL Database eight out of 10 because I believe nothing is perfect.
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.
Sr. Software Engineer at a hospitality company with 1,001-5,000 employees
It's easier to set up than the on-prem version, saving us time
Pros and Cons
- "We've saved time setting up the databases. While I'm not involved in the maintenance, I'm sure that's also a big factor. It's hosted in the cloud, so we don't have to maintain the servers."
- "I rate Microsoft Azure SQL Database 10 out of 10."
- "Some more documentation and suggestions for network policies could be helpful."
What is our primary use case?
I use Azure SQL for data storage and querying for applications.
How has it helped my organization?
Azure SQL works well. Our applications are hosted in AKS, and we can easily do the security and authentication. It's easer to set up than an on-premise SQL database, so that has had a positive effect on our productivity.
We've saved time setting up the databases. While I'm not involved in the maintenance, I'm sure that's also a big factor. It's hosted in the cloud, so we don't have to maintain the servers.
What is most valuable?
Azure SQL is really straightforward to use. It's nice that it's just SQL but in the cloud. We've switched from the on-premise SQL databases we use and have Azure SQL for some of our more recent stuff. It's seamless.
The AI applications sound neat. We haven't really gotten to do that yet, but we like that it works so well with Fabric. It seems like something we could easily connect.
What needs improvement?
One thing we struggled with was the network stuff. We had to figure out how to ensure we were secure. That part took a bit, but we're in a great spot now. We had to work with security to figure out our network policies. We're in a private instance, so you can only connect to it from our VPN. We've made some progress, and it's much easier to use now. Some more documentation and suggestions for network policies could be helpful.
For how long have I used the solution?
We have used Azure SQL for a couple of years at this point.
What do I think about the stability of the solution?
The stability is great. I haven't noticed any problems with it so far.
What do I think about the scalability of the solution?
The scalability is useful. Unlike our on-premise SQL Database, which is not easily scalable, Azure SQL allows us to increase the tier and get more performance as needed.
Which solution did I use previously and why did I switch?
We switched from on-premise SQL databases to Azure SQL for more recent projects because it's easier to set up in the cloud without dealing with complex network rules.
How was the initial setup?
We have a lot of people who are experts in Microsoft SQL stuff, so switching to Azure SQL was just a piece of cake for them because it's basically the same thing.
What about the implementation team?
We used our internal team, who are experts in Microsoft SQL, to switch to Azure SQL, finding it to be a seamless transition.
What other advice do I have?
I rate Microsoft Azure SQL Database 10 out of 10.
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.
Buyer's Guide
Download our free Microsoft Azure SQL Database Report and get advice and tips from experienced pros
sharing their opinions.
Updated: October 2026
Product Categories
Database as a Service (DBaaS)Popular Comparisons
MongoDB Atlas
Microsoft Azure Cosmos DB
SingleStore
Azure Database for PostgreSQL
Google Cloud SQL
Oracle Database as a Service
Google Cloud Spanner
Couchbase Capella
Oracle Exadata Express Cloud Service
Oracle Exadata Cloud at Customer
Yugabyte Platform
IBM Db2 on 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?



















