What is our primary use case?
My main use case for Azure SQL Managed Instance is for storing information related to insurance and claims in the staging database to avoid using Dataverse because it is more expensive.
I use Azure SQL Managed Instance to store claim information, which allows me to save the data there. Typically, I have a retention period of 30 days in my own Dataverse. Once the data is moved from Dataverse to Azure SQL Managed Instance, I immediately delete that data from Dataverse. The retention period in Azure SQL Managed Instance is eight years, and I display that data on Dataverse by using the OData API in the virtual table.
What is most valuable?
The best features Azure SQL Managed Instance offers, in my opinion, are scalability, security, database size, and costing. It is much cheaper than Dataverse storage and other competitor products.
Cost stands out to me most among scalability, security, database size, and cost. I have found the security features in Azure SQL Managed Instance to be robust and effective in my experience.
Azure SQL Managed Instance has positively impacted my organization by reducing a significant impact on our budgeting for the financial year.
What needs improvement?
Azure SQL Managed Instance can be improved by adding more scalability options.
I need to have more flexibility in terms of scalability with Azure SQL Managed Instance. In sizing, I need some options available so that it can be scaled up or scaled down based upon my requirements.
For how long have I used the solution?
I have been using Azure SQL Managed Instance for the last three years, but at this location I have been using it for the last one year.
What was our ROI?
I have been able to save somewhere close to 45% in cost since using Azure SQL Managed Instance.
What other advice do I have?
My advice for others looking into using Azure SQL Managed Instance is that if they have some SaaS applications such as Dataverse or any other SaaS applications like BPM or ServiceNow, wherein their SaaS application-based database has higher costs incurred to it, they should definitely select Azure SQL Managed Instance so that they can save on keeping the data there. Organizations often have a larger retention period; for instance, in the insurance domain, you have a retention period set to eight years for any record saved within the SaaS application. With those kinds of retention periods, you need to ensure that it is in a cheaper storage option, yet it should be a robust storage option.
Security-wise, Azure SQL Managed Instance is absolutely robust, and governance-wise, the manageability of Azure SQL Managed Instance is very good. You can manage it from a console as well as from user interfaces. I am not aware of the AI capability as I have not yet explored it, so I cannot comment on that.
I don't have any experience working with Azure SQL Managed Instance's AI capability regarding its accuracy and reliability of output. I would rate this review an 8 overall.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
