Microsoft Azure SQL Database vs Redis comparison

"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."

"Azure SQL is easy to integrate and simplifies things from a licensing perspective. We're comfortable with SQL versus other types of databases, so we feel better talking to Microsoft."

"Emergency mode is quite useful."

"This solution offers high availability, and business continuity is in place."

"The hardware is all managed by Microsoft."

"We've cut costs by around 70 percent."

"What I like about SQL Azure is that it's similar to your on-premises SQL databases. It's not much different, so it's easy to start quickly on the solution if you know Microsoft SQL. I find its ease of use most valuable, and I also like that SQL Azure is also easily integrated with the Azure Cloud platform."

"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."

"The solution is fast, provides good performance, and is not too expensive."

"Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you use Redis efficiently."

"The in-memory data makes it fast."

"The solution's technical support team is good...The solution's initial setup process was straightforward."

"The most valuable features of Redis are its ease of use and speed. It does not have access to the disc and it is fast."

"It is particularly efficient for cloud-based storage and operations."

"Redis is a simple service that does what it promises."

"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."

"The solution could improve by allowing the export of the data more seamlessly. It is difficult to copy and back up data."

"I haven't explored SQL Azure's features much, but I would like to see some better integration with Python."

"The solution can be improved by reducing the cost so more users can be added."

"SQL Azure could improve the feature set. They are catching up to Microsoft SQL Server."

"We haven't had any major issues that have prevented us from doing stuff fundamentally. For its implementation, sometimes, it is complicated to understand what your needs are. It would be good to have a few use cases that provide different cloud variations that match on-premise installations and show how they can be moved to the cloud a bit better."

"Adding users to Azure SQL could be easier. You need to script it out, but it would be nice if it had a UI where you can click and add them."

"We've had many concurrency issues with it, particularly with applications that do a lot of parallel processing."

"Operational cost needs improvement."

"The tool should improve by increasing its size limits and handling dynamic data better. We use the client ID or associate it with a key for static content. The solution will not be easy for a beginner. Unless you understand SQL data, it will be difficult to understand and use Redis. It also needs to be user-friendly."

"I would prefer it if there was more information available about Redis. That would make it easier for new beginners. Currently, there is a lack of resources."

"Redis presents a single point of failure and lacks fault tolerance."

"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."

"Redis should have an option to operate without Docker on a local PC."

"The solution's pricing for a local installation is very expensive."

"For the PubSub feature, we had to create our own tools to monitor the events."

"There is room for AWS to provide more options for server types or a way to configure more or less memory for them."

"I am not aware of the exact pricing, but our monthly bill for Azure is around 80,000. It is less expensive than using SQL Server. It has the pay-as-you-go model, and the charges are based on the usage."

"SQL Azure's licensing cost is expensive."

"The pricing is actually complicated, and that is probably one downside of it. In some respects, although we can plan for the costs on a month-by-month basis, we are finding it hard to project our costings for it. Fundamentally, Microsoft is offering two pricing models, and it is challenging to understand the differences between the two. We're basically on the DTU model at the moment. That may change in the future as the size grows, but it is one of those things that we'll end up monitoring as we progress. At the moment, to get a reasonable response, generally, the price is a little high for us, but it is one of those things for which we know that we can do improvements on our code. So, it is not just the service that's the problem; it is some of the things that we need to do as well."

"The pricing is flexible and can be adapted based on our requirements but the pricing options are complex especially if we are using a VM."

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

"The solution is expensive."

"The price of the solution is reasonable."

"The license is based on the number of users."

"Redis is an open-source product."

"Redis is not an overpriced solution."

"We saw an ROI. It made the processing of our transactions faster."

"Redis is an open-source solution. There are not any hidden fees."

"The tool is open-source. There are no additional costs."