Increase the number of databases limit
The current limit of databases in a SQL Managed Instance is 100.
In our current situation when migration our SaaS products to Azure, we have over 4000 sql databases (one pr customer).
We would really love to skip managing our SQL VMs ourselves, but we are not really ready for jumping right to Azure SQL and Elastic Pools.
Our Database Administrators run scripts the old fashioned way and looping through thousands of databases in a script. This is not possible with Azure SQL and Elastic Pools.
But if we go for SQL Managed Instance, we would get over 40 managed instances, and that is too many in our opinion.
If the limit had been increased to 500 databases, we would immediately scrapped our SQL VMs and went for Managed Instances instead
Jordi Meijer commented
We are running into this similar issue. We have over 2000 SQL databases and we're hoping this limit of 100 databases can be increased.
Jing Kan commented
Although we can add more instances to support more databases, we still want to scale up without change our service level logic.
We hope the limit can be shifted considering resource utilization. We ended up getting another Managed Instance due to the same issue but resources are underutilized. I am not sure if using MIs was the best choice in terms of cost-effectiveness.
Kyle Nunery commented
Running into a similar issue. We have close to 600 sql databases so we cannot use SQK Managed Instance without significant application changes.