Microsoft Azure SQL Database Reviews

Our company uses the solution for on-premises production and PR. We sync data from the database service to our on-premises SQL server. 

The SQL connector effectively syncs data to our database. 

The default 1433 port for communication should be customizable because most hacks or attacks are attempted when creating any application or database on the default port. The solution should allow use of any custom port. 

I have been using the solution for more than three years. 

I also used the solution and handled its administration at my previous job with a government entity.

The setup is straightforward so is rated an eight out of ten. 

We implement the solution in-house. 

I rate the solution a nine out of ten. 

Our primary use case is creating management-related items for SQL for the development of a variety of items we are working with.

I would like to see the cloud connectivity environment improved.

I have been using SQL Azure for the past year or more.

The stability is excellent because it is easier for us to connect to the cloud rather than connecting to MSSP.

When it comes to scalability because it is a cloud, you can always get additional resources, or you can scale up. At the point of integration, we have over three hundred. We created three instances, housing, roughly about one hundred of them, and then whenever we have additional disabilities, and we have maxed out on the number of instances, we just create another instance and start there, waiting for disabilities in that management. This is easy to notice on the cloud. Your resources are things that you can easily scale up without having to wait for hardware.

We have contacted technical support. The organization has a very good partnership with Microsoft and any area of the solution that can use even the on-prem risk premium platform. If I have issues on the network or with Nigel, I contact the account manager and I am directed to the appropriate team at Microsoft. If other users on the databases are syncing, I just reconnect to how I log a ticket on a Microsoft phone call and engineers are able to work with me to resolve the problem.

The initial setup was a bit difficult.  There was a faulty management style that we created, but we were able to replicate it subsequently because you can do a number on each of the management styles.

I believe the licensing is more on a global scale.

I would rate SQL Azure an eight out of ten.

I'm currently involved in setting up pipelines on Azure for data extraction from a source to a target destination within specific time intervals. The goal is to automate the process of moving data efficiently.

Previously, the database was on-premises, but now, with the SQL database in the Azure cloud, extracting information from on-premises automatically makes it available in the Azure cloud. The data becomes instantly accessible in the cloud, making it more efficient for you to work with. It's a straightforward and easy process.

One of the most valuable aspects is its seamless integration with Azure Data Factory. Its value lies in the significant time savings as there's minimal competition or customization challenges. This smooth integration makes it easy for me to work with both seamlessly.

There is room for improvement regarding the pricing structure. It would be beneficial if the cost is reduced.

I have been working with it for more than a year.

The system is impressively reliable and stable. I would rate it ten out of ten.

I would rate the scalability capabilities eight out of ten.

I've had a positive experience working with their technical support team. I would rate it nine out of ten.

Positive

I currently use the Sophos server management solution, which is an on-premises solution. The primary reason for switching to SQL Azure is our plan to migrate to cloud.

The initial setup used to be a bit complex, but now it's much easier. I would rate it eight out of ten.

The deployment process is remarkably quick, taking only a few minutes to connect to the cloud and set up data storage. There's a standard setup without the need for additional or advanced deployment tools. It is handled by a dedicated team, constituting around three to five percent of the overall process. This includes individuals responsible for deployment, validation, and user support, ensuring a straightforward and efficient deployment experience.

The return on investment is a significant advantage for our company, especially since we've implemented this product across multiple distributions and clients. The satisfaction of our clients with the product support is notable. I would rate it nine out of ten.

I find that they are relatively expensive, especially when compared to AWS, where the prices are notably lower.

I would highly recommend it. Overall, I would rate it nine out of ten.

The solution is used for a lender's business application. 

The scalability and simple management of the infrastructure are the most valuable features. 

They have some problems with the introduced features in the latest version of the server. The multiple query planning parameters have problems. The problem is the automated configuration. Even when they address the problems, there are still issues.

The second issue is to audit the real users on behalf of whom we operate secret servers. Normally in our application, we use only a single connection to leverage the pooling.

I have been working with SQL Azure for eight years. 

The solution is highly stable. I rate the stability a ten out of ten. 

The solution is hugely scalable yet it does not support auto-scaling and it is very time-consuming. The PR database takes a lot of time hence one should keep another server synchronized with the dataset. Presently, ninety thousand users are using the solution. I rate the scalability a six out of ten. 

The technical support is very good. 

The initial setup is very straightforward. 

I would rate the pricing a seven out of ten. 

I would rate the overall solution a nine out of ten. 

I am using SQL Azure for migrating existing SQL Databases into the cloud. 

The most valuable features of SQL Azure are its reliability and quick scalability.

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

I have used SQL Azure for approximately nine years.

SQL Azure is highly reliable and stable. I have not had a problem.

I rate the stability of SQL Azure a ten out of ten.

The solution is highly scalable.

SQL Azure offers a large number of scalability targets, such as memory and CPUs, and the disc given is highly configurable. The speed it takes to scale from one level to the next is fast.

We have approximately 100 people using the solution, which are mostly virtual developers.

We plan to increase our usage, we are migrating Google databases to SQL Databases.

I rate the scalability of SQL Azure a nine out of ten.

The support is good, but sometimes it takes a while to receive the resolution.

I rate the support of SQL Azure an eight out of ten.

Positive

I was previously using SQL Server.

You are responsible for managing SQL Server on your own. Furthermore, although you have paid for the SQL Server license, it is now based on the number of cores and can be quite costly. However, it has more features than SQL Azure.

The initial setup of SQL Azure is simple because it is in the cloud. There is not a lot to set up. If you do it manually, it can take five minutes. If it is done through DevOps pipelines, such as TerraForm, then it could take twenty seconds.

I rate the initial setup of SQL Azure a nine out of ten.

The price of the solution is reasonable.

The affordability of the solution allows for the swift and effortless creation of proof of concept projects to determine if it is suitable for their needs.

SQL Azure has all the enterprise features I need. To create enterprise solutions for a fairly good price point.

I rate SQL Azure a nine out of ten.

About 25 people in my office use SQL Azure. Including customers, there are about 400-500 people.

We have multiple applications running for our customers that we can integrate into Azure SQL.

Scalability is an issue because we can't upgrade to new versions due to hardware limitations. 

I've been using SQL Azure for a couple of years.

I rate SQL Azure nine out of 10 for stability because we haven't faced any major issues.

I rate SQL Azure six out of 10 for scalability.

We haven't used technical support because we haven't faced any major challenges, but I would rate their documentation and knowledge base eight out of 10. 

Positive

I rate SQL Azure eight out of 10 for ease of setup. In the worst-case scenario, deployment takes a few days. A couple of employees could do it easily. Usually, it's an admin and a developer. 

I rate SQL Azure six out of 10 for ROI. We've seen a 40-50% ROI

I rate SQL Azure eight out of 10 for affordability. I live in a developing country where cost is always an issue. The price should be negotiable, and there should be more discounts.

I rate SQL Azure eight out of 10. I recommend it because we haven't faced any major issues. 

I think this product can improve its integrations with business intelligence software. The integrations are always cumbersome due to the approvals, passwords, et cetera. 

I have been using this solution for the last three years.

My impression is that this solution is quite stable. I would rate its stability an eight, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the scalability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best. Currently, there are two users of this solution in our company.

I will be doing the implementation myself with the help of a third party.

We evaluated the SQL Server in addition to this solution, but we ultimately chose Azure mainly to have everything on one platform.

Overall, I would rate this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

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.

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.

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.

I have used this solution for almost six years.

I would rate the stability as eight out of ten.

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.

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.

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.

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.

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.

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.

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.