We use Azure SQL serverless or with virtual machines.
Azure SQL is used mostly by my clients for ETL.
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.
We use it for supporting an application from another platform to Azure.
Operational cost needs improvement.
I have been using SQL Azure for 6-8 months.
It is a stable solution.
It is a scalable solution.
The initial setup is straightforward. The designing process is involved in the deployment.
Overall, I would rate the solution an eight out of ten.
We are using SQL Azure for databases that are hosted in Microsoft Azure.
SQL Azure is reliable and scales well.
The solution could improve by allowing the export of the data more seamlessly. It is difficult to copy and back up data.
I have been using SQL Azure for three years.
I rate the stability of SQL Azure an eight out of ten.
We have approximately 1,000 people using the solution in my organization.
I rate the scalability of SQL Azure a nine out of ten.
The support is good.
I rate the initial setup of SQL Azure a nine out of ten.
The solution is expensive.
I rate SQL Azure a nine out of ten.
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 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 are deploying a few server-based applications, and we are using the Azure SQL database.
It provides good analytics. We can see which database is getting more requests, etc. We are able to see everything in Azure SQL. Its analytics are in a readable format, so a layman can understand them.
Its performance is good. It has a lot of features. It has the backup feature, which is not there in Amazon RDS. In Azure SQL, there is an option to replicate and restore a database point to point, whereas we can't do that with Amazon RDS.
It is also simpler and more powerful than Amazon RDS. It also has analytics, and it automatically suggests a few things. It has an in-built indexing function.
In terms of support, they don't give much support.
I have been using this solution for four to five years.
There are more than 12,000 people using this service. Its usage is going to increase day by day.
They don't give much support, but their tech support subscription cost is much lesser than AWS.
Its installation is very easy. We can easily move from one pool to another pool in Azure. It takes just one to two minutes.
We take care of it ourselves.
It only has a subscription-based license.
I would recommend this solution to others. I would rate it a ten out of ten.
We use the solution as a customer database for travel desk applications.
The solution suits well for our server requirements. It doesn't require an extensive system to run. So, it is a fast, limited, and affordable database serving our business purpose.
They should include more accessible functions for image tooling. Presently, we are using optional features for it.
I have been using the solution for about two years.
The solution is moderately stable. I rate its stability an eight out of ten.
It is a scalable solution. We have around 200 solution users in our organization. I rate its scalability an eight out of ten.
The solution's technical support team is good.
Positive
Previously, I used Microsoft's on-premises version.
The solution's initial setup was straightforward. I rate the process an eight out of ten. It took one or two days to deploy it. Since it is cloud-based, we followed the standard Azure mechanism.
The solution is moderately expensive. I rate the pricing a six out of ten.
One should be clear about their reporting environment. For instance, Microsoft ecosystem reporting supports only Power BI. Secondly, one should ensure they utilize more customization options than already issued.
I rate the solution as eight. It is a familiar product for users who already work on Microsoft environments. If you need a limited cut-down version, it also has an option for a single database.
It is simply our relational database.
It has cut our costs. That's the big thing.
Cost savings are the most valuable. The DR/high availability is also valuable. The failover group with the built-in DR/high availability features is probably one of the easiest things.
Its automation can be improved. SQL Server Agent was a very big part of the on-prem tools. While moving from on-prem to the cloud, redoing some of such tools was very cumbersome in Azure. There was a whole new set of technologies and methodologies. It should have easier automation-type features to be able to implement such tools. It should have almost a SQL agent type of substance built into that.
I have been using this solution for five years.
It is very stable. It has been in our production environment for three and a half years, and we have had only one significant outage.
Its scalability is pretty high. Its ability to scale is very good. We're actually in the process of migrating on-prem to Azure, and its scalability is very easy.
In terms of the number of users, there are probably a hundred technical people who are leveraging the technologies. They are developers, administrators, and the BI group.
The setup was pretty straightforward. The networking aspect was non-intuitive, and it was probably the biggest stumbling block when we initially set it up.
We have our DevOps processes that we follow in our deployment, so we establish those initially, and there was a significant amount of testing done prior to putting it into production. On a scale of one to five, it was probably a three in terms of time and effort to get it all implemented.
For its maintenance, there are probably five or six of us, but one person can also maintain it if required.
I don't have specific numbers, but we were able to cut down the size of our data center by 80%.
I have an annual spend number, and it is in the hundred thousand dollar range. There are no additional costs to the standard licensing fees.
Even though you have to look at the cost numbers of what you're going to be charged on a monthly basis, what you have to also remember is that your application may need a lot of rewriting and things like that. You get charged not just for the monthly costs but also for the transactions that occur. If your access to the data layer is not so efficient, your costs will go up because you're pulling far more data than you potentially need. These are hidden costs that nobody ever considers. If your application is not written very efficiently, you may actually increase your costs over on-prem versus cloud.
We are a Microsoft shop. The biggest thing that we probably looked at was AWS. We also looked at some of the Oracle cloud solutions, but we went with Azure only because it just integrates with all of our stuff, and it cuts our costs.
I would rate SQL Azure an eight out of ten.