Microsoft Azure SQL Database Reviews

We use many different vendors in private equity because we own real estate, and we have numerous different data sources that we need to import. We are planning to move to Fabric soon because we have disparate data from different management systems as well as from our HR platform and various other sources, so we want to compile everything into one centralized location.

Our data engineers find Microsoft Azure SQL Database easy to work with, and my role as a product manager allows me to translate requirements to them in a straightforward way. We have excellent data engineers, so ease of use is the primary factor.

The effectiveness of Microsoft Azure SQL Database security features in meeting our compliance standards is crucial because we are SEC compliant, and that is one of our main criteria for compliance; otherwise, our investors would be very upset.

I have not used Microsoft Azure SQL Database intelligent performance features.

I am unfamiliar with Microsoft Azure SQL Database automatic tuning.

The challenge we face is that we need to implement an alerting system to notify us when issues occur, which is a problem for later. We are fortunate that we do not have many of those instances, but that is definitely a challenge we will need to address at some point.

I wish the customer service and technical support were a bit quicker, though I recognize that not everything can be solved within an hour or a day.

I have been using Microsoft Azure SQL Database for approximately three years.

I wish the customer service and technical support were a bit quicker, though I recognize that not everything can be solved within an hour or a day.

On a scale from one being the worst and ten being the best, I would rate my customer service and technical support a seven.

I give the customer service and technical support a seven based on the response rate, though the responses I have received are very good and have pointed me in the right direction. We have implemented our solutions; it is just about timing.

Prior to adopting Microsoft Azure SQL Database, we had servers on-premises, so fortunately when we moved to Azure, we did not need to handle that transition, though I cannot speak to that process as it occurred before my time.

My experience with deploying Microsoft Azure SQL Database has been pleasant and straightforward, but I have had excellent engineers to guide me on exactly where I should go and what I should be doing, so the process has been very positive for me.

Since we continue to use Microsoft Azure SQL Database year after year, I suppose we have seen a return on investment.

My experience with the pricing, setup costs, and licensing is that it is fortunately not my department; my VP handles that.

My VP is very firm about keeping everything within the Microsoft suite of products, so I do not even know if he evaluated other solutions before selecting Microsoft Azure SQL Database because we wanted to stay all Microsoft. So, you received a home run with that.

I would not know if Microsoft Azure Active Directory integration and Azure Key Vault have helped manage data security; I believe our data engineers would have that answer.

The compatibility with other SQL servers for transitioning legacy systems to Microsoft Azure SQL Database is probably moderately important, as they need something to work with. If it is something they need to learn, it is not the end of the world, but the less they have to onboard different systems, the better.

My data engineers would have better examples of how the features of Microsoft Azure SQL Database have benefited our organization than I would.

One thing I plan to do in the next year with Microsoft Azure SQL Database is create more of a sandbox and testing environment and maintain consistent refresh data between the two. Currently, we refresh monthly, which is insufficient for my testing needs and for training and onboarding. In the next year, we plan to establish a more streamlined workflow to create sandbox and test environments.

The advice I would give to another organization considering Microsoft Azure SQL Database is to evaluate what is most important to the organization and determine if it aligns with what Azure provides. Our company is fully committed to Microsoft, which is fortunate, but the key is to understand your actual needs; if you want more control and more ownership of the system, that is not necessarily the value proposition of this service. We want you to maintain it for us and manage everything for us, so I would recommend creating a thorough list of requirements. I would rate this product a seven overall.

We use Microsoft Azure SQL Database to store restaurant sales data within the food and hospitality industry.

As the Azure SQL Database provides automatic backups, it gives us peace of mind knowing that we have backups and the restore capability available. Additionally, it is quick to set up and offers scalability. As our needs increase, we can easily scale it up to handle more data and faster processing.

Some of the best features of Microsoft Azure SQL Database are its scalability, pricing, and ease of setup. It is quick to set up and easy to scale. 

As our data needs increase, scaling up is as straightforward as dragging a slider to increase processing speed. The product also offers automatic backups, giving us peace of mind about data security. 

For the features we receive, the price is very reasonable.

One area for improvement is the need for accurate cost estimates. When I initially tried to set it up, I could not get an accurate quote on what my monthly costs would be based on my needs.

I have used Microsoft Azure SQL Database for a couple of years.

I have never experienced any downtime with Microsoft Azure SQL Database. It has been completely stable.

I would rate the scalability a ten out of ten. Scaling the solution is incredibly simple and involves just clicking a button or dragging a slider.

The customer support is hard to reach, with Microsoft’s technical support being difficult to get in touch with. While support exists, you have to be very patient to reach the right area, and communication is mainly through email chats rather than speaking to someone directly.

Neutral

I have only used Microsoft SQL Servers during my 15 years of experience. I have not used another cloud database.

The initial setup of Microsoft Azure SQL Database was straightforward and took only a couple of hours to complete.

The return on investment includes time savings, backup, and security features that minimize worry. It is a cost-effective solution at about $100 a month. It is ensuring we receive what we pay for through the blend of price, performance, and features.

While the pricing of Microsoft Azure SQL Database is good, obtaining an estimate of monthly costs based on specific needs was challenging. Initially, Microsoft asked us to sign up and use the service to see what it would cost.

I have not evaluated other SQL database solutions, since my familiarity is with the Windows environment, leading to the choice of Azure.

I would recommend Microsoft Azure SQL Database to others. For the price, you get an excellent balance of features and performance. I would suggest exploring AWS, although I am not familiar with its setup or the feature-to-price ratio.

Our main use case for Microsoft Azure SQL Database is mostly to serve as the backend for our enterprise applications.

The feature I like the most about Microsoft Azure SQL Database is that it's a managed service, which is the main reason we use it. As a global enterprise, we used to spend a lot of time maintaining SQL Server and SQL Databases. Using Azure SQL allows us to leverage our people's comprehensive power to focus on more important tasks than just upgrading the SQL and doing maintenance.

The effectiveness of Microsoft Azure SQL Database security features in meeting compliance standards is very important for us, as tracking the setup for our on-premises databases was very hard, especially when our team grew. Now, in combination with Azure Policies, we have strict control over the policies and setup of our databases, along with good results from vulnerability scanning and other tools that help us advance towards a well-managed environment.

I think the question of how Microsoft Azure SQL Database can be improved is a good one, but to be honest, I need to ask my operations teams as I'm not sure what the best area for enhancement would be.

Rather than thinking about the flaws, I would enhance Microsoft Azure SQL Database with more AI or perhaps even cheaper prices; everybody would prefer everything to be cheaper. However, I don't see any real flaws, especially since it helped me prove that it's a good service, so I'm a really happy user.

The idea is to make it cheaper, as always. Cost is indeed an area for improvement, but it's a general observation.

I would say that we started using Microsoft Azure SQL Database quite early, about seven years ago, during our first attempt to migrate databases and start building new applications using Azure SQL.

My experience with customer service and technical support is dependent on the issue. For simple queries, it usually goes smoothly, but more complex issues tend to lead to tough discussions and often require escalation to our Microsoft contact due to slower response times. When we need support, it's typically urgent as we have a capable team, and backend issues require quick resolution from the provider.

Neutral

My company did not consider other solutions before choosing Microsoft Azure SQL Database, as it was a natural advancement given that we are based on Microsoft products. After thirty years of using Microsoft products, it just made sense, especially since everything integrates seamlessly into Entra ID, making it difficult to switch to other clouds.

Describing my experience deploying Microsoft Azure SQL Database, I find it easy because we run our infrastructure as code, with templates aligning with our policies and standardized architectural blocks. For us, it's like a vending machine; someone orders a database, and they get a consistent database every time, only tweaking the SKU or some minor settings for specific requirements.

The biggest return on investment for us when using Microsoft Azure SQL Database is that it's a managed service, which means we don't need to manage upgrades ourselves. This is crucial for an enterprise like ours that primarily does manufacturing. This is vital as we can maintain the same number of people in our operations teams even as our company grows quickly.

Regarding trying to use another solution while using Microsoft SQL, could you clarify whether you mean Microsoft or Azure alternatives?

We are exploring options like PostgreSQL or other databases while using it, but our team's extensive experience with Microsoft products keeps us primarily using Microsoft SQL. After seeing announcements about new features that might bring some PostgreSQL functionalities into Microsoft's ecosystem, I am excited to explore those options further.

My advice to other companies considering Microsoft Azure SQL Database is to try it and realize how much it alleviates the burden of managing SQLs, especially since something typically goes wrong in critical situations. Azure SQL significantly reduces the number of failures, and I'd recommend using Azure Migrate to assess databases and test with the first solution, even checking pricing as you might be pleasantly surprised; it's a really worthwhile solution. I would rate this review an eight out of ten.

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.

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.

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.

Regarding Microsoft Azure SQL Database, I have worked with the product for around one year or a longer period of time.

Regarding the stability of Microsoft Azure SQL Database, it is stable.

I find it easy to scale Microsoft Azure SQL Database.

I would rate support for Microsoft Azure SQL Database as nine out of ten.

Positive

I have already used Oracle database earlier in my career, which is different from Microsoft.

In terms of installation, it is not complicated, actually; it is quite simple.

I purchased it from Azure only.

The pricing for Microsoft Azure SQL Database is a bit high.

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.

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.

I use Azure SQL Database as a reporting repository. We have clients who use Epicor ERP. I replicate portions of that database into Azure SQL Database for clients to use for Power BI or other reporting.

Additionally, I have niche use cases, such as using it as a witness in an RDP farm or a SQL high availability group. We have a couple of small websites using it as their primary data store, but the majority of use cases are for reporting and business intelligence.

We have integrated it with Microsoft Copilot agents as well as things like Power BI. We are also doing replication with on-premise or VM-based SQL Servers. It seems a little bit more complex to use Azure SQL Database as a data source for Microsoft Copilot add-in. There is a fairly complex setup to use it as a data source, but it is possible for sure. Otherwise, for things like Power BI and business intelligence, it is fantastic.

It is less expensive than doing a full-blown virtual machine for some of the lightweight loads, but I cannot give any numbers.

Azure SQL Database is very quick and easy to use. It certainly makes my infrastructure and development teams more efficient.

It is fantastic for business intelligence purposes.

There are compatibility issues that prevent Azure SQL Database from being a direct replacement for SQL Server running on a virtual machine. For instance, handling application-initiated DBCC commands is a challenge.

We had occasional compatibility issues which sometimes were showstoppers. If we have an application that we do not control, such as SolidWorks, when we try to deploy it using Azure SQL Database, it blows up because it is trying to make a call to the database that is not supported. It is like a black box to us. We do not have the ability to do anything other than go with a different SQL, for instance, SQL running on a VM. There are command compatibility issues with SQL Server standard.

I have been using Azure SQL Database for more than eight years.

The latency and availability of Azure SQL Database have been fantastic. We have had no issues with it.

While scaling, it can be a bit laggy. 

First-line support is challenging as they tend to be not very helpful. It usually takes an escalation or two to reach someone who can truly assist me. Once I reach the right people, the support is incredibly knowledgeable and thorough, but there is a delay in getting to the right people.

Neutral

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.

I looked at other Microsoft options such as SQL Managed Instance or SQL in a virtual machine. I also considered the data store option running in Amazon Web Services but ultimately found Azure SQL to be easier and cheaper. The performance and cost were the main reasons for going for Azure SQL.

Microsoft’s expertise in SQL Server was very important when considering cloud database options. 

I would advise verifying application compatibility. Also, make sure that you review your security configuration and that you are following the guidance from Microsoft on security configuration.

I would rate Azure SQL Database an eight out of ten.

Microsoft Azure SQL Database serves as our main database for our application and microservice infrastructure.

What I appreciate most about Microsoft Azure SQL Database is that the infrastructure is managed by Microsoft, which means we do not need to worry about patching, relieving significant time from our engineers.

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. Moving to the cloud saves us not only engineering hours for operations but also helps us manage our spiky website traffic more effectively.

I would change Microsoft Azure SQL Database by removing the four terabyte limit and reconsidering how the database cores relate to the storage.

I have been using Microsoft Azure SQL Database for four years.

My experience with Microsoft Azure SQL Database's automatic tuning has revealed that while we have been using it, we realized the SQL database index that was created was somehow reverted a few days later, likely because of the nature of how our application behaves due to random and spiky web traffic. This may indicate the index was added but reverted later, which was likely caused by our application behavior contributing to this outcome.

I have not used the intelligent performance features of Microsoft Azure SQL Database. Microsoft Azure SQL Database's security features, including Defender for Database, meet our compliance standards as it helps us check all our permissions, roles, and accounts, alerting our team in the event of any changes made, and ensuring we address vulnerabilities detected by Defender for SQL Database.

Regarding customer service and technical support from Microsoft, we are currently on a mission-critical support plan, and the engineers provide timely advice. In one incident involving website outages due to high database I/O, the engineers helped pinpoint the exact problem and guided us on how to resolve it.

Positive

Before choosing Microsoft Azure SQL Database, I was using an on-premises legacy system.

My experience with the deployment process of Microsoft Azure SQL Database is straightforward, as we are using Entity Framework to deploy our database changes and Terraform for the infrastructure. Using Entity Framework to deploy our database schema has been good without any problems.

The biggest return on investment for us when using Microsoft Azure SQL Database is the time savings since we do not need to manage SQL database updates regularly as it is now fully managed by Microsoft.

My only concern regarding the pricing, setup cost, and licensing of Microsoft Azure SQL Database is that we have a large database size but limited compute requirements, which has forced us to move towards a higher core just to meet our database sizing requirements. We will be checking with the SQL database team on how to transition from our current setup to eventually a hyperscale database.

My advice for other companies considering Microsoft Azure SQL Database is to understand their database requirements and, if they have a larger data size, to consider Managed Instance before committing to SQL Database. I rate this product a nine out of ten.

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.

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.

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.

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.

I have been using Microsoft Azure SQL Database for about 15 years.

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.

Microsoft Azure SQL Database allows easy scaling up and across without the need for physical infrastructure adjustments.

We did not switch from another solution because we are a Microsoft-oriented company and have seamlessly used Microsoft products for many years.

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.

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.

Microsoft Azure SQL Database serves as our database after we migrated a database to the cloud and we're checking it out to see if that will be somewhere we want to go with a lot more of our applications.

Managed Instance is the feature of Microsoft Azure SQL Database that I like the most.

I have not yet used Microsoft Azure SQL Database intelligent performance features.

My experience with Microsoft Azure SQL Database automatic tuning is intermediate, but it has definitely helped because it takes a lot of the guesswork out of manually going through and finding what could be causing some bottlenecks.

I assess the effectiveness of Microsoft Azure SQL Database security features in meeting compliance standards as pretty good.

Microsoft Azure Active Directory integration and Microsoft Azure Key Vault have helped me manage data security.

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.

One example of how these features have benefited my organization is backup and recovery, which is almost identical to how we do it because as DBAs, your most important job is to make sure the data is available.

Microsoft Azure SQL Database could improve by providing more support for Availability Groups within Managed Instance.

We have been using Microsoft Azure SQL Database for eight months now.

One challenge we faced deploying Microsoft Azure SQL Database was refreshing the databases because we keep copies of them and refresh them to other environments.

I would describe my experience with customer service and technical support as excellent, from the few times we have had to reach out.

Positive

We were using a similar solution previously, which was SQL Server on-premise.

Latency and how strong support would be if something goes wrong stood out in my evaluation process before selecting Microsoft Azure SQL Database.

We have seen a return on investment.

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 cost.

When it comes to licensing costs, it is a lot cheaper when you have Managed Instance versus a standalone SQL server.

Use the tools that Microsoft provides to assess your current environment if you are considering using Microsoft Azure SQL Database. I would rate this overall review as a nine.