What is our primary use case?
We use SQL Azure to store our relational data. Whenever I have complex relational data with consistency requirements, I use SQL Azure Database.
I'm currently working in a small startup. There are just two people using this solution now: a developer and myself. I'm working as a technical consultant and an architect.
What is most valuable?
Microsoft recently added a JSON feature. I use all the features in a normal relational database, and they're very helpful. I prefer using Microsoft SQL Server because I like the experience and the way Microsoft handles the query tuning and security. These are really good features for database experts.
What needs improvement?
One of the nice features in Microsoft SQL Server is the SQL Server CLR, which we sometimes need to protect our procedures using C# or CLR. This feature isn't available in the SQL Azure database. It's available in the Managed Instance in the Azure Database.
You can create SOAR procedures using C# and can get user-defined functions using C#. You can extend the database and the data files using CLR files. This feature isn't available on the Microsoft Azure SQL Database. I understand they can't add it because it's a managed service, and having CLR probably doesn't work for them, but it would be nice if they could add this feature.
For how long have I used the solution?
I have used this solution for almost six years.
Buyer's Guide
SQL Azure
April 2024
Learn what your peers think about SQL Azure. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
769,976 professionals have used our research since 2012.
What do I think about the stability of the solution?
I would rate the stability as eight out of ten.
What do I think about the scalability of the solution?
It is very scalable, depending on how much you're willing to pay. We can have up to 4,000 DTUs, but we haven't needed that much scalability.
How are customer service and support?
We had an instance where we weren't able to deploy Cosmos DB on a UAE data center, and Microsoft helped us. We haven't had any issues so far with technical support.
How was the initial setup?
Setup is straightforward. You just create an SQL Server instance account on Azure, and then you can create SQL databases. It's very easy to create tables and procedures. I mainly use the SQL data buckets inside Visual Studio. From there, I deploy databases to Azure from Visual Studio.
What about the implementation team?
It's easy to do the deployment in-house. Visual Studio provides a lot of functionality to make deploying solutions to Azure simple and easy.
What was our ROI?
Using SQL Server database with all the features will provide a good return on investment. Once you move to Azure, you remove all the capital expenses by having to acquire the license and deploy it on-premises.
What's my experience with pricing, setup cost, and licensing?
When you go with SQL Azure Database, you can create a small database, which is around $4 to $5 per month for development purposes. It's very cheap in that respect. I think it's a little bit expensive compared to other services that Microsoft offers on Azure. PostgreSQL, MySQL, and MariaDB are a bit cheaper than SQL Server.
If the price were lower, I think it would become more attractive for developers to use.
What other advice do I have?
I would rate this solution as eight out of ten.
It's a very easy solution. Microsoft also has Data Explore. The entire Microsoft environment makes things easy for developers. It's very easy to set up SQL on Azure. I highly recommend it. I really like it, and I've been working with SQL Server since 2000.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.