Microsoft Azure SQL Database Reviews

Our primary use case for SQL Azure is to operate our database.

The features I like most is that it offers a lot of securitt verification and backup from our side as well as from within SQL Azure.

Security can sometimes be a problem when it affects our business needs. It needs to integrate more security without stopping the service or our business. In some cases we have a lot of restriction on people who needs to use the database for whatever reason. We need more performance but in the same way we need more security - from the application and also in the Internet. The problem is therefore in the internet. 

The stability is good at the moment. We are more dependable on the stability from the internet from our service provider. The solution is responsible for 99% of the stability, but most of our problems are due to our local internet provider.

The scalability is good. We have 100 users and one can upgrade the system by performance and by the size of the storage. You can move between different types of storage using block or docket. You can use any way you choose without losing data. So the scalability it is very good. We plan to increase our usage.

We are planning to redo the assessment about whether more people should be involved in the technical support. 

The initial setup was very complex. It is hard to explain, but the problem is when you have more than one service. We have only one service but the solution has multiple capabilities. 

The deployment team installed the solution on one machine at a time, so it took very long. I chose a big database and within less than nine minutes I was able to collect data. So that was much faster.

We used a vendor team and they have one or two guys who are responsible for the maintenance. 

When it comes to implementation, my advice would be to integrate between Microsoft platforms. I will rate it an eight out of ten as I would love to see faster integration.

I use the solution for database maintenance. 

The environment is user friendly and there is good flexibility for adding modules or features. 

The solution effectively handles storing and maintaining information in databases. 

The solution requires familiarity with its language so can be tricky. A simplified language would be appealing to users. 

A more user-friendly format for certain modules is desired. 

The application and interface can be a bit heavy to install.

I have been using the solution for one year. 

The solution is stable. 

The solution is scalable. It takes a bit of knowledge about the process but then is really easy.  

I have not needed technical support. 

The setup can be a bit of a challenge until you get used to it. Once you have familiarity with it, setup is okay and takes about 30 minutes. 

A colleague assisted me with implementation. 

I recommending using the solution because it is effective and user friendly. 

I rate the solution a nine out of ten. 

I have used SQL Azure for the backend tier application. If the customer has the flow change application with an application service, they will use the backend. I always suggest using SQL Server and Azure.

The backup solution in Azure is great, the firewall settings in SQL are very easy to use and work very well. Additionally, the turning process is very good and has improved the SQL services and queries.

SQL Azure could improve by adding more features.

I have used SQL Azure within the past 12 months.

I have found SQL Azure to be stable.

The scalability of SQL Azure is very good.

The support of SQL Azure is very good.

The implementation of SQL Azure is simple.

I would recommend this solution to others.

I rate SQL Azure a nine out of ten.

We don't have to manage it much. It is managed by Microsoft, which makes it easy for us because there is no admin overhead for managing the servers. 

It is also easily scalable. During peak hours, it can scale higher.

We have a very small database running on SQL Azure. We have not been able to load bigger systems on it. It is still not something that is feasible. All our heavy-duty systems are on SAP, and it should have more compatibility with other vendors such as SAP. 

Its price can definitely be lower. It is pretty pricey.

We've been using SQL Azure for about three years.

It is stable.

It is easily scalable. We have five people who are working with this solution.

Their technical support is very good for SQL Azure. Basically, based on my experience, we usually don't have any problem with support for Microsoft products. If we are seeking support for something like Linux or something that is not exactly a Microsoft product, it is a little disappointing.

Its price can definitely be lower. It is pretty pricey.

I would rate SQL Azure a seven out of ten. It works like any other SQL database, and it is pretty good.

We are using it for processing financial transactions. We have its latest version.

Azure Portal is most valuable.

Service Broker should be added in Azure Cloud. Service Broker is currently available only in the on-premises version.

I have been using this solution for two years.

It is stable.

It is scalable. We have six users and two people in our technical team for its deployment.

I haven't used their support. I have only used the online material, and that's complete.

We used PostgreSQL, which was on-premises.

It requires a license. As compared to its competitors, such as Oracle, it is affordable and reasonable.

I would recommend this solution to others. I would rate SQL Azure a nine out of ten.

We are using SQL Server both on Azure and in a Spark environment, on-premises.

The most valuable feature is PolyBase.

The product is very user-friendly.

I feel that the price is high and it could be reduced.

I have more than 14 years of experience in the Microsoft Data Warehouse platform.

SQL Azure is very stable.

This is a very scalable product.

I am the only person in my company who uses it.

I have not been in contact with technical support.

The initial setup is straightforward and I don't find it complex.

Overall, I am happy with this product and I recommend it.

I would rate this solution a nine out of ten.

We use it for a few databases that are deployed for our own purposes. 

SQL is a simpler database. We use it more than other databases. 

I have been using SQL Azure for three to four months. 

We haven't had any issues with performance. 

There are only three users who use it. Once we are more comfortable we will give it to more users. My technology team uses it. 

Microsoft technical support is good. 

Pricing is reasonable for a big enterprise. The price is a little higher. It should have a 20% discount. 

I would rate SQL Azure an eight out of ten. 

We like the collaborative nature of the solution. It's the most valuable aspect of the solution.

The stability of the solution is very good.

The availability of resources could be improved.

The solution needs to offer online training to help improve the capacity of teams to manage the SQL.

The pricing is very high.

I've been using the solution for two years so far.

We haven't had any issues with the stability of the solution. There aren't bugs or glitches. It doesn't crash or freeze. It's reliable for us.

We haven't had any issues with the solution, therefore, we haven't required any technical support. I can't speak to the quality of technical support as I've never dealt with them.

In the beginning, we decided to use a specialist to configure all the systems for us and the solution is almost perfect.

The price is very high, especially when you compare it to other solutions. There aren't extra costs, however. All fees are included in the licensing package.

We're simply customers. We don't have any professional relationship with Azure.

I would recommend the solution. It's great.

I'd rate the solution nine out of ten. I'd give it perfect marks if the pricing was more reasonable and if they offered better learning tools to guide our staff.