Microsoft Azure SQL Database Reviews

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.

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.

My main use case for this solution is hosting application databases.

The feature I like the most about Microsoft Azure SQL Database is the scaling part.

It is cost-effective, which is why I appreciate that feature.

I find Microsoft Azure SQL Database very easy to use. Some basic knowledge from Azure is needed, but then you can use it quite easily.

I am using the automatic tuning feature in Microsoft Azure SQL Database for some applications. It scales when there is more need for performance, so that has been the impact on my database performance.

The solution's security features, such as using Defender, have a positive impact on my data protection strategies. Defender helps protect our data.

I think Microsoft Azure SQL Database should be cheaper. The license is expensive, but not always; it depends on the case regarding pricing and licensing. The cost could be lower in some cases.

I have been using Microsoft Azure SQL Database since 2016.

I have not experienced any real issues.

I find it scales workloads well; it scales automatically if you use the correct settings.

I have had experience with customer support and technical support, but not for SQL. The experience is sometimes good and sometimes not as good; it depends on the person you get and the product overall for Microsoft.

Neutral

I sometimes used Azure SQL Managed Instance before choosing Microsoft Azure SQL Database. The reason I use the other one is based on application requirements; that is the only reason.

If it is possible, I would consider switching to Microsoft Azure SQL Database completely, but most applications I have do not support any other tool, so I have no choice.

The deployment and the migration process of this platform are easy and straightforward.

It has helped me reduce my company's total cost of ownership.

I do use Azure Hybrid Benefits. I have seen less cost as a benefit since implementing this feature, and it is cheaper.

We are exploring the usage of AI in our company. I think Microsoft Azure SQL Database has a place in that AI environment.

I do not know about Microsoft Azure SQL Database's ability to power next-generation AI applications since I have not used that feature, so I only have information from the marketing slides from Microsoft and the sessions, but I have no real experience.

I use the native backup option and have experience with the backup and restore functionalities. It works so far. I assess the reliability in terms of maintaining uptime and availability as good.

Microsoft's expertise in SQL Server is not important to us when considering cloud database options. My advice for other companies thinking of getting Microsoft Azure SQL Database is to use it. They should start with a proof of concept and a test environment, and then if it is successful, roll out to the production environment. I would rate this solution an 8 overall.

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.

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.

My main use case for Microsoft Azure SQL Database is hosting an in-house application to serve different business streams.

The feature I like the most in Microsoft Azure SQL Database is the recovery point of time to recover the database when needed.

These features have benefited my organization by improving response time in seconds and milliseconds, and this will improve customer experience and satisfy the commercial team as well.

Microsoft Azure SQL Database can be improved by getting recent recommendations from Microsoft's side to be applied on a quarter basis, such as the latest batch update.

In a POC, I have been using Microsoft Azure SQL Database for one or two years.

What worked with Microsoft Azure SQL Database is good, but the challenge I faced is that it does not fit for a large-scale or tier-one business application.

I would evaluate customer service and technical support for Microsoft Azure SQL Database as very good.

On a scale from one to ten, I would rate service and technical support an eight because it needs improvement, especially for accelerating support or solving a problem immediately or having expertise available around the clock, because there might be a mid-tier experience from the support team, and in some cases, we need to involve an expert immediately to solve our cases.

Positive

Prior to adopting Microsoft Azure SQL Database, I was using another solution such as PostgreSQL and Oracle databases in place, and we have open sources as well in place, such as Mongo SQL or Mongo database.

I would describe my experience with deploying Microsoft Azure SQL Database as good.

I have seen a return on investment with Microsoft Azure SQL Database.

The return on investment I can share is that it improves customer experience, and improving customer experience means getting more customer base to use our products, and this is ROI for using such products.

Before selecting Microsoft Azure SQL Database, I considered other solutions such as Oracle and PostgreSQL.

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

My experience with Microsoft Azure SQL Database's automatic tuning is that the database should be optimized and tuned very well, either by doing something to enhance the performance or by consulting support teams to give advice to be applied, such as the latest patch set, or to analyze queries to get optimizer feedback to be applied immediately in order to get applications tuned all the time.

I assess the effectiveness of Microsoft Azure SQL Database's security features in meeting compliance standards as compliant with our security rules.

I have not seen Azure Active Directory integration and Azure Key Vault help manage data security.

The capability with SQL Server for transitioning legacy systems to SQL Databases is important to me as we depend on a famous database technology such as Oracle, but we need to mix and match our technologies in terms of databases and SQL as well, such as Azure SQL, in order to have heterogeneous environments, not depending on one solo vendor. We are trying to move a mid-tier or a small tier to Microsoft Azure SQL Database.

My advice to other organizations considering Microsoft Azure SQL Database is to move a mid-tier or a small team to Microsoft Azure SQL Database. I give this review an overall rating of seven.

My main use case for Microsoft Azure SQL Database is to connect source data for our APIs and hydrate different things for that.

I appreciate Microsoft Azure SQL Database because I enjoy SQL. It works well out of the box, and I know what I'm getting. The product functions as expected without requiring much maintenance.

Microsoft Azure SQL Database benefits my company on a day-to-day basis as it serves as an excellent place to store our database and data. I would appreciate the ability for all teams to operate on one database instead of several different systems. Microsoft Azure SQL Database is one of those solutions that helps consolidate our infrastructure, though unfortunately it is not the only solution we use.

I think Microsoft Azure SQL Database can be improved, but I do not use it frequently enough to identify significant pain points.

In my area of expertise, I have been working for about three years, and in my current position, I have been using Microsoft Azure SQL Database for only about one year.

Regarding reliability, I would generally consider Microsoft Azure SQL Database quite reliable in maintaining uptime and availability.

My impressions of Microsoft Azure SQL Database's ability to scale workloads are positive. I think it works very well with no complaints.

Microsoft's expertise in SQL Server is very good when considering cloud database options. I have not used the support myself, but the documentation is very up-to-date. If I ever need to look something up, it is quite easy to find.

Positive

We have different solutions implemented across our organization. I know that we have some relational and some non-relational options, which is probably part of the reason for having multiple systems. The main differences between those solutions and SQL would be the relational versus non-relational aspect. We use a lot of legacy software, so that probably plays into some compatibility aspect. Beyond that, I am not certain about other differences.

Other than the relational versus non-relational distinctions, I am not entirely clear on why we maintain these different solutions.

The migration and deployment process of Microsoft Azure SQL Database is quite straightforward. If I ever encounter issues, Copilot is quite helpful, as is the documentation. I would not say it is very complicated.

From my point of view, the biggest return on investment with Microsoft Azure SQL Database is that it is great to store our customer data and everything for our different products and be able to access that easily as we want to. I do not know what we put into it, so I am not certain what that looks like from an ROI perspective. However, it works smoothly, I have no complaints, and it is a good database solution.

Microsoft Azure SQL Database has probably helped reduce my company's total cost of ownership.

I have never looked at the pricing, setup costs, and licensing for Microsoft Azure SQL Database.

I am not considering switching away from Microsoft Azure SQL Database or conducting a proof of concept of another solution.

I would rate Microsoft Azure SQL Database as a five on a scale from one to five in terms of ease of use.

I assess Microsoft Azure SQL Database's ability to integrate with other Microsoft applications as excellent, with no complaints.

I have not had hands-on experience with Microsoft Azure SQL Database working with AI. I know that functionality exists, and part of what I am trying to focus on at Ignite this year is learning how I can integrate different AI solutions and workflows with Microsoft Azure SQL Database.

I am not using the automatic tuning feature in Microsoft Azure SQL Database.

I do not know what impact Microsoft Azure SQL Database's security features have on my data protection strategies, if any.

I am not using the data encryption feature on Microsoft Azure SQL Database, or at least not knowingly.

I have not used the backup and restore functionalities of Microsoft Azure SQL Database. Our database engineers have touched that before, but I have never used it. It seems to work as intended.

We are still using other solutions alongside Microsoft Azure SQL Database.

My advice for other companies that are considering Microsoft Azure SQL Database is to go for it, especially if you are using other Microsoft products. It seems to integrate with everything very well, and it just works.

I have rated this review a nine out of ten overall.

My main use cases for Microsoft Azure SQL Database are third-party applications.

The features of Microsoft Azure SQL Database that I appreciate the most are Availability Groups.

My organization benefits from consolidation efforts with these features.

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

User permissions authentication to Microsoft Azure SQL Database is something that has been helpful.

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 any comments at this time.

I have been using Microsoft Azure SQL Database for less than a year.

I have not used Microsoft Azure SQL Database intelligence features.

Regarding my experience with SQL Database Automatic Tuning, I have not used it yet.

I have not raised any issues regarding customer service and technical support.

On a scale from one to ten, I would rate customer service technical support a seven.

I would probably give that rating based on my previous history opening up other support cases with Microsoft.

Positive

Prior to adopting Microsoft Azure SQL Database, I was using on-premises SQL Server environments to address similar needs.

The adoption of more Azure services led me to consider a change.

I have no comments describing my experience with deploying Microsoft Azure SQL Database.

I faced no challenges, but it was seamless because I already had Microsoft Entra and Active Directory set up with seamless permissions and an established environment.

Before selecting Microsoft Azure SQL Database, I considered Postgres.

What stood out to me in my evaluation process was the ease of getting the third-party application to support SQL Server.

I am currently looking into transitioning legacy systems to Microsoft Azure SQL Database to perform an on-premises migration from SQL infrastructure to Azure SQL.

In this particular use case with Microsoft Azure SQL Database, it actually moves many of the hurdles away. Hosting these types of databases on-premises can be challenging, but if you have the ability to do it on Azure, that is beneficial, and it also removes security obstacles as well.

I have no comments on anything they can improve on, change, or any additional release I would like to see.

I would rate this review an eight overall.