Microsoft Azure SQL Database Reviews

We decided to implement some forms for different purposes. We needed to implement it on-premises, so we did this on Azure to support the data from the forms implemented on a SQL server, and on Azure on several databases. It's very easy. 

The solution is quite straightforward to set up.

It can scale. 

The solution is stable and reliable. 

I want the pricing to be improved. They should try to lower it for their customers. 

I've used the solution for one year.

The stability is good. There are no bugs or glitches, and it doesn't crash or freeze. 

The solution can scale. I can't say how much as I don't have a comparable use case on the cloud and on-premises. 

We have about five people using the solution right now. For now, we do not have plans to increase usage.

The support is good. They have a good document library. If there is a problem, we can figure it out. 

The initial setup is very straightforward. It's not complex at all. For us, it did not take more than one or two hours. It was quick to deploy. 

We only need one person on hand for deployment and maintenance. They are a developer. 

We did not use a consultant for the implementation process. We have a lot of experience in Azure and a lot of systems in Azure as well. 

We have a yearly licensing fee we need to pay. It's not a cheap solution. 

I'd recommend the solution to other users. 

Based on the experience I've had, I would rate it seven out of ten. 

We're using it for scalability. Everything is on Azure SQL for us. It is an enterprise application data warehouse, so all our applications are on this. It is useful for entire data warehousing. It is also good for microservices applications. We have its latest version.

It is good for scalability and high availability. It is also secure because of Microsoft's cloud investment.

It is easy to use because it is on the cloud. Creation or making it available through web services is super easy. Azure SQL can be quickly published as web services for APIs to connect with other applications. Because it is in Microsoft Cloud, you can easily integrate with Microsoft stack.

Its price could be better. It is expensive.

I am not sure if Microsoft Master Data Services is included in this. If not, Master Data Services can be integrated with Azure SQL. I have only used Master Data Services on-premises.

I have been using this solution for four years.

It is stable. Microsoft has been in the market for quite some time.

It is quite scalable. It is a good choice for any kind of application database, data warehousing, or data lake. 

In terms of the number of users, it is being used by all users in our enterprise. For development, we have four to five developers, and we also have partners to help us.

Technical support is managed by Microsoft partners, which is good.

Positive

We have used Microsoft SQL Server on-premises. We are still using it, and slowly, we'll move to Azure SQL.

You don't have to install it because it is on the cloud.

It is expensive. Snowflake and PostgreSQL are cheaper than this. Google is also cheaper than Azure. 

Its licensing is on a pay-as-you-go basis. It is based on usage and storage.

I would recommend this solution. If anybody is using Azure Cloud, they should definitely use Azure SQL. Our strategy is to have all our applications on Azure, and we will keep using this solution. We will also be using it for our analytical data mart.

I would rate SQL Azure a nine out of ten. It is a good product, and it has all the required features.

We use SQL Azure for what we call an inspection round. Inspection rounds are mainly used by an inspector in the field to check the compliance of the equipment, like if a given machine doesn't have enough instrumentation. 

In any kind of plant, there is an inventory of assets. Most companies have an inspector who goes to the field to check the condition and record some indicators. The results of the inspection are recorded in our software. All the data from the inspection round is stored in our database in Azure. That is what we use the Azure database for.

We created a custom PaaS. It's not a pre-built device in the cloud. Azure components like SQL Azure and a web server are combined to create this solution. Our SQL performs better in that space than a readymade device.

The most valuable aspect of SQL Azure is the SQL language itself. It's open and everybody can use it at my company. Also, we thought in the beginning that the response time would be inadequate, but it's actually decent. It's much better than expected. Then again, I'm not a programmer, but that's what I hear from our development team. 

There are some characteristics called "joins," like "inner join," "full join," "left join," "right join," etc. It's a little confusing for some coders. I think that could be simplified. 

I'm in the analytic space, so I would introduce a higher level of coding using artificial intelligence. SQL is quite close to English. They could add a voice interface where you speak into it, and the machine writes the code for you. My weakness in coding requires something automated, so I can be more proactive. 

They should also simplify the security in Azure. We are using the cloud as a platform, so there is no physical infrastructure. We're using Azure components like databases and servers to create an application. Integrating those components in terms of permissions and security is challenging for us. Maybe there is a lack of knowledge on our side, but it's not straightforward. 

The data modeling is not good for me. There are better tools than SQL Azure when you need to create the abstract part of the database design. It's weak. It's not user-friendly, and the notation is specific to Microsoft. I believe we use a third-party tool for data modeling because it's easier to use. Communicating with that tool is easier than SQL Azure. The model is nicer.

I have been using SQL Azure for about five or six years. We started using the solution for one of our clients, a mining company, more than five years ago. They were the first customers to use our solution.

We don't have any issues with stability. The primary issues in the cloud are privileges, security, and integration between applications. That is a total mess for us. When we need to get the application servers access to the Azure database. 

SQL Azure is scalable.

I only contacted Azure support once, and it was decent. We asked some questions, and they replied. I cannot it say was great or awful. They met our expectations. 

Setting up SQL Azure is easy. Even I can do it. 

We pay around $1,200 per year for one customer based on what they currently use. It's mainly processing and storage. SQL Azure is a bit more expensive than other solutions. There are free databases, but they don't have the scalability of the Azure cloud. It might not be affordable for some companies, but it's highly scalable.

I rate SQL Azure eight out of 10. I would recommend it to others depending on their needs. It might be beyond the budget of some companies.

Generally, what I like about Azure as a cloud is the analytics you can apply on top of that data. Azure provides a number of high-performing solutions for data science and analytics. The main issue is that you need to build the architecture to create a product that provides value for your customers.

It's about imagination and creativity, and most of the tools are there. In my case, ease of use matters because I lack the knowledge to explore more, but our development team could do that easily. 

We use Azure SQL serverless or with virtual machines.

Azure SQL is used mostly by my clients for ETL.

The most useful feature of Azure SQL is the queries for manipulating the data, such as the tables and the storage processors.

Azure SQL can improve by adding more machine learning features like other databases, such as Cassandra or Cosmos DB.

I have been using SQL Azure for approximately three years.

Azure SQL is a stable solution.

The scalability of Azure SQL is good. However, it is limited by the infrastructure. The cloud version gives more scalability.

The support from Azure SQL is good.

I rate the support from Azure SQL a four out of five.

The initial setup of Azure SQL is of a medium level of difficulty. We need some expertise in installing, configuring, and deploying Azure SQL.

We have approximately 20 to 30 specialists for the deployment of Azure SQL.

The price in general of Azure SQL could improve.

We have enterprises in Chile, Peru, Spain, Italy, and Colombia that provide IT services. We use this solution every day to maintain new projects and use the on-premise and cloud versions.

My advice to others is to review alternatives to Azure SQL. For example, SQL Serverless, SQL with a virtual machine, or Azure SQL Instances.

I rate Azure SQL a nine out of ten.

SQL Azure is used for the replication of a CRM database. if get information from this database and try to replicate it on other servers and other systems. I'm getting the transactional data information.

The most valuable feature of SQL Azure is centralized authentication because I'm using the domain, user name, and password, for Microsoft 365 account with multifactor authentication and the security has been working well.

I was using a user list for connecting a program in OTF for getting information. The connection in SQL Azure can improve by being easier because at the moment I have to use private certificates for user authentication. I had to do additional configuration to have the connections.

I have been using SQL Azure for approximately six months.

SQL Azure is stable, I have not had any issues.

The scalability of SQL Azure is easy to do.

We have a lot of people in my organization using this solution. We have a large company.

I have not used support.

The initial setup of SQL Azure is difficult and complex. I have to use a lot of certificates, private keys, and public keys to establish a connection.

SQL Azure is a really good tool. I recommend using this solution instead of a normal SQL server, its an improvement,

I rate SQL Azure a nine out of ten.

We use it also for database management, as a database engine.

We use it for different projects - mainly when we have lots of data and the customer can't afford to pay the license for SQL Server, which is not cheap. That's the main reason we use MySQL or Postgres or other databases. 

The management and the remote access in SQL Azure are seamless.

The solution is extremely scalable.

We've found the stability to be quite good.

It's the type of product that doesn't need much technical support assistance as it works seamlessly.

Some data types are not available on SQL Azure while it's available on SQL Server. It's a little bit limited in terms of functionality. The difference is not huge. You can go back and forth between them. We used to do this all the time. However, it is something to note.

Maybe they need to add the data types that exist in SQL Server, not in SQL Azure. That would make it better.

The pricing can be high in certain countries as Microsoft doesn't adjust for regional pricing. 

The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. The performance is good.

The product is on the cloud. It's very scalable for that reason. If a company needs to expand it, it can do so.

Most of the time no one needs support on SQL products or services. That said, the support in Azure is amazing. We never encountered an issue that they didn't solve. This speaks to the quality of Azure.

We also use SQL Server. The main difference is SQL Server is a full-featured database engine, whereas MySQL is based on what we call a file-based database, which is similar to flat files as a database engine.

The recommendation of which to use is based on the use case. It depends on what use case the customer will need. If they don't have the capacity to manage their own server, I would recommend Azure, as it's managed. You don't have to worry about the management and administration.

The pricing is prevalent for everything Microsoft. The thing is, they don't allow different pricing for different regions. Some countries are price sensitive.

I'm an end-user.

I'd rate the solution at a nine out of ten.

We use this solution to store data MODS that are going to be consumed by Power BI.

The solution is quire more stable than other tools.

I would like to the solutions scalability to be improved.

I have used this solution for the past three years.

This is a stable solution in general.

It is moderately scalable in my opinion. On-premise, you can definitely scale it up better, but it is a bit restricted on the cloud.

We used Oracle Databases and SQL Server databases on-premise.

The initial setup was easy for about five hundred users and it required just a couple of managers.

Our consultants helped with the implementation and the process took maybe ten minutes.

I would recommend this solution for those who are looking to integrate it. I would rate this an eight out of ten.

We have multiple use cases for this solution, and it really depends on the application team requirements. Our analytics team uses it. We also use it for database migration.

What I found most valuable in Azure SQL are the functions related to Active Directory and the database services. You can do everything in Azure SQL.

Integration needs to be improved for this solution.

We've been using Azure SQL since 2013.

Azure SQL is a stable solution.

Azure SQL is scalable.

We had to contact technical support about some of our issues, and it was good. They have good people.

Installation for this solution is very easy, but you'll need to be a certified installer to find the setup easy.

We implemented Azure SQL through an integrator and data partner.

Azure SQL has licenses which you can pay yearly or monthly. You have the option to pay yearly or monthly for the license.

Microsoft Azure is something that we are using. We are using Microsoft Azure from the Cloud. It's the public cloud we are using. We use multiple services on Azure, e.g. mDNS, Traffic Manager, Database, etc., depending upon the attributes and aspects. We're using Azure SQL.

We have a cloud team made up of 10 people who use this solution, then there are various application teams that also use Azure SQL. At the moment, we have no plans of increasing usage for this solution, but we're open to it.

I would recommend this solution to others looking into using it.

I'm rating Azure SQL a 10 out of 10.