What is our primary use case?
Our primary use case for this database is internal apps that we create. Those apps are generally transactional, so we write back and/or collect data from them and house that data within SQL.
The other use case is bringing in data from external sources, manipulating it the way we want to see it, and storing it in a SQL database.
How has it helped my organization?
I do not come from a traditional, hosted SQL Server background. I just fell into Microsoft Azure SQL Database at the company where I work, so I do not know the exact benefits. However, I know that I would not want to be spinning up servers, installing a SQL Server instance, and doing all the infrastructure-related work, because Microsoft takes care of that. You just pay for what you use, and that is about it.
These features have added value to our workload. They have made things easier so that we do not have to go out and explore or build on our own. It is built in, and you just turn it on.
What is most valuable?
The feature I appreciate most about Microsoft Azure SQL Database is the shortcutting feature, which is really nice. We were heavily invested in the Fabric ecosystem, so having Microsoft Azure SQL Database allows us to shortcut into our Lakehouse and then build reports and dashboards on top of that. That really helps us. The uptime and not having to manage those things, letting Microsoft take care of the backend infrastructure, is also really nice because it is point and click for what you need.
We are utilizing the AI features within Microsoft Azure SQL Database, such as hybrid search. We are starting to dabble in that a little more. We are not using it at a production level yet, but we are definitely experimenting and looking at what value it could provide, because we are trying to create something similar outside. If it is already built into Microsoft Azure SQL Database, then we might as well just use that.
Our use is in-house. We are not putting it out in front of the public or people outside of our company, so it is very internal. Security is still a concern for us, so we use whatever features SQL provides. We have not dabbled much further than that because we do not have to be compliant or regulated.
Azure Active Directory integration and Azure Key Vault have helped us manage data security. I think they have changed the terminology from Active Directory to Microsoft Entra ID, but it is the same thing. That helps a lot to keep data roles and security in place and makes everything a lot easier to manage.
Compared to adding users all the time, the Entra ID integration is what helps us. If we have a security group created in Microsoft Entra ID, we just name the group and manage everything in Microsoft Entra ID. We do not have to do it at the SQL level. Previously, we may have had to do that at the SQL level, or we had to create some sort of script that would update the SQL Server when the Microsoft Entra ID group got updated. That integration really helps.
I do not really manage the Microsoft Purview and Microsoft Defender for Cloud side of things, but I know that whenever there is a legal ask or we need to trace data or documents and where they all come from, Microsoft Purview really helps. I talk to my administrator, and he can go into Microsoft Purview and give me all the details. The traceability is really phenomenal.
What needs improvement?
I know that integrating within the Microsoft ecosystem is a great start, and I think the more they do that, the better compatibility it will have with other services. I know some of the connectors are premium, so if we could get a lower cost, I think it would be a little easier and there would be no barrier to entry.
Right now, we were trying to utilize Microsoft Azure SQL Database with Power Apps, but it requires a premium connector. We shy away from things like that because we are already paying for Azure SQL, and then we have to pay for connecting to Azure SQL. That is a barrier to entry, where you drop one of the two and say, "Okay, we have to save cost, so let's not do Azure SQL. Let's do something else that is more of a free product within the ecosystem." I think a tier-based pricing model would help, where if you are not hitting a certain amount of writes or reads, it is free, and if you go above that, you start to pay.
For how long have I used the solution?
I have been using Microsoft Azure SQL Database for about the past four years.
What do I think about the scalability of the solution?
We have not expanded our usage much since the initial deployment. As I said, it is internal, so we are not getting high utilization on it. I have played around with the features, and it is really good. It is just point and click, and you say you want more capacity, and it does its thing in the background.
How are customer service and support?
I would evaluate Microsoft support as subpar. We have worked with Microsoft support quite a bit on other issues not related to SQL. With those other issues, they ask the same questions about what we have already done, even after we have provided all the evidence we have collected. I would rather they look at everything we have provided before asking multiple questions, then assess, and then have a conversation. It is hit or miss depending on who you get.
We have a Microsoft rep for Fabric and that whole ecosystem, so I have a direct line with them. Whenever I run into an issue, I can send a quick Teams message and ask for suggestions or what to do before reaching Premier support. Even with Premier support, we get a load of questions back, whereas they should really be doing the digging. We have had a hit-or-miss relationship with support. I understand they have a lot of customers, but we pay for it, so I do not want them to ask us questions as if to say, "You figure it out." That is how we would deal with any other managed service provider. If we had somebody running that sort of support for us, I would expect them to provide that level of digging around and to make sure they understand the problem, rather than coming back with 20 questions and expecting us to answer. It is always a question of whose court the ball is in.
I would rate support a five out of 10, or even below sometimes.
How was the initial setup?
I was not involved in the deployment of Microsoft Azure SQL Database. It was already configured and in place, so I just manage it or build on top of it.
Which other solutions did I evaluate?
As I said, we are a Microsoft shop, so we do not utilize anything else.
What other advice do I have?
I would rate Microsoft Azure SQL Database about eight out of 10. It is pretty good and pretty up there. There are probably other use cases, but for our use cases, I highly rate it.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure