I use Azure SQL Database as a managed relational database for storing and querying application data without worrying about infrastructure. It's great for building scalable apps since it handles backups automatically. It takes a lot of the operational headache off my plate, so I don't have to manage servers, patching, or backups manually, saving me lots of time. I really like how it takes care of backups, updates, and high availability automatically, allowing me to focus on building features instead of maintaining infrastructure. The database scales easily depending on the workload and integrates well with Microsoft tools. The initial setup was pretty straightforward, as the Azure portal guides you through creating a database step by step. Review collected by and hosted on G2.com.

It can get expensive if we don't monitor usage closely. Review collected by and hosted on G2.com.

What I like most about Azure SQL Database is how little you have to manage it handles scaling, patching, and high availability automatically so you can focus on building.

It also integrates really smoothly with the wider Azure ecosystem, which makes it easy to plug into apps, analytics, and security tooling without a lot of setup. Review collected by and hosted on G2.com.

Less control and potential cost spikes at scale are the main drawbacks of Azure SQL Database. Review collected by and hosted on G2.com.

I really like Azure SQL Database because it takes very little time to administer. Automated backups, patching, and high availability are all handled for me, which frees me up to focus on other work. I also appreciate the elastic pool feature, since it lets me manage multiple databases with different usage patterns without overpaying. Integration with Azure Directory makes security straightforward, and the built-in performance insights help me spot issues and optimize queries more easily. Review collected by and hosted on G2.com.

There are a few areas that could be improved. To start, the pricing model can get expensive once you need more DTUs or vCores, especially when you compare it to running a VM with SQL Server. Also, some features still feel missing, such as cross-database queries. Finally, troubleshooting performance can be frustrating at times, since wait stats and query plans aren’t as detailed as they are with on-prem SQL Server. Review collected by and hosted on G2.com.

Azure SQL Database is that it’s a fully managed, highly available database service that lets teams focus on building applications instead of managing infrastructure.

Azure handles patching, backups, monitoring, and high availability automatically, which significantly reduces operational overhead. I especially like its built-in security features such as Azure AD authentication, transparent data encryption, auditing, and threat detection.

From a scalability perspective, the ability to scale compute and storage independently, use elastic pools, and switch between service tiers makes it very flexible for both small applications and enterprise workloads.

Another big advantage is high availability and disaster recovery by default, with SLA-backed uptime and features like active geo-replication. Since it’s fully compatible with SQL Server, it also makes migration to the cloud much easier without major application changes. Review collected by and hosted on G2.com.

One thing I find a bit challenging about Azure SQL Database is that some advanced SQL Server features are limited or not fully supported, such as cross-database queries in certain scenarios or SQL Server Agent jobs for scheduling. This sometimes requires workarounds, like using Elastic Jobs, Logic Apps, or Azure Functions, which adds extra steps. Review collected by and hosted on G2.com.

I like that Azure SQL Database is very easy to use, especially since I come from a Microsoft environment. I also appreciate SQL Server Management Studio. The price is very affordable and the pricing mechanism makes it easy to adjust, whether we need to scale up or down. I like the easy integration with many platforms we currently use, which includes being part of the Microsoft ecosystem since we're heavily invested in it. There's a seamless integration with Azure Data Factory, which is very powerful. Review collected by and hosted on G2.com.

The learning curve can be a bit tricky at Microsoft. Review collected by and hosted on G2.com.

I love how it's quick to create a new virtual server and databases, and it's impressively low maintenance. I appreciate the great scalability Azure SQL Database offers and the fact that it always uses the latest SQL server version. It creates an easy pathway to ingest data into Microsoft Fabric using mirroring, and I find the quick scaling and deployment very helpful. Review collected by and hosted on G2.com.

I don't like that Azure SQL Database doesn't allow cross-database querying, and many tasks require T-SQL rather than offering a GUI option. Also, when restoring a database from a backup, you can't do so over an existing database; you have to create a new database on the virtual server. More GUI options similar to traditional on-premises setups would make it easier to use, along with more options around backups and restorations. Review collected by and hosted on G2.com.

It’s one of the best cloud-based RDBMS options. It’s also part of Microsoft’s legacy software stack. We have full control to create or modify indexes, procedures, functions, spatial data, and more. Review collected by and hosted on G2.com.

In my previous organisation, we were able to monitor live SQL queries using the built-in monitoring tools in SSMS. Review collected by and hosted on G2.com.

Help a lot using the Database, because it manages the design and the architecture with the cloud of Microsoft Azure, the integration can be automaticallty this help a lot and saves money and time implementing the database to production. Review collected by and hosted on G2.com.

Well, the maintenance has to be improved because it can remove backups if you do it automatically, so the best is to do it manually and do it yourself, so that way the database will be safe.

Also you can not run this data if you do not have Azure first, and you do not paid the cloud, it will be impossible to use SQL. Review collected by and hosted on G2.com.

The best thing about Azure SQL database is how easy is to work with. setting it up was quick and straightforward, and I didn't need to spend hours figuring things out. It has so many features that make managing data simple, and I use it frequently because of its reliable and easy. The great thing is customer support, they are responsive and helpful and overall, it's a good experience from start to complete. Review collected by and hosted on G2.com.

it's a bit expensive as your usage grows, especially if you need higher performance. Sometimes the pricing feels a little confusing too. Also, while it's generally easy to use, there are moments when advanced configuration can be tricky if you are not very technical. Apart from that. it works well, but cost and complexity at scale are the main downsides for me. Review collected by and hosted on G2.com.

The best thing about Azure SQL DB is its reliability and dynamic scalability. It promises no downtime for databases, so users don't need to worry about maintenance or potential outages. Its resilient architecture and high-performance database engine contribute to a dependable experience. It's easy to implement and integrate with variety of the business applications having multiple tech stacks support. Review collected by and hosted on G2.com.

There are still some features that have not yet been developed, such as limited server agent functionality, and the absence of database mirroring or clustering. It also lacks certain traditional SQL features. Additionally, Windows Authentication is not supported, so you have to rely on Entra ID (with Azure AD). For legacy applications built on proprietary .NET code, support is significantly reduced, and in some cases, almost nonexistent. Review collected by and hosted on G2.com.