Azure-docs: Limits for Managed Instance

[bootleg224]

Is the 100 databases / instance a hard limit or a recommendation of a max? If it is a hard limit, will other tiers support larger limits (e.g. 500 databases per limit), similiar to elastic pool?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 28ca1f7f-5a34-0f23-10ce-3ff24c76db97
• Version Independent ID: 5c4a22c4-78fc-911d-9fa0-8dfab1653b6e
• Content: Azure SQL Database Managed Instance Overview
• Content Source: articles/sql-database/sql-database-managed-instance.md
• Service: sql-database
• GitHub Login: @bonova
• Microsoft Alias: bonova

[Mike-Ubezzi-MSFT]

For reference:

In the Managed Instance service tier section of the referenced document, there is a figure of 100 databases per instance:

[Mike-Ubezzi-MSFT]

@bootleg224 Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

[bootleg224]

Hi team, checking in, any update?

[Mike-Ubezzi-MSFT]

@bootleg224 I have reached out to the SQL Community to get an answer back to you.
Regards,
Mike

[Mike-Ubezzi-MSFT]

@bootleg224 The 100 databases per (Managed) instance is a soft limit based upon an average of workloads. If you require more than 100 DBs (or your use case calls for more than 100) the Azure SQL product group would like to hear more about your scenario(s). That information can either be detailed here with this GitHub issue, emailed to [email protected], or that can be detailed on the SQL User Voice feedback forum, where other users can vote in support of and provide comments about.

Thank you,
Mike

[bootleg224]

Currently running an IaaS SQL Server that has similiar specs to some of the Managed Instance offerings. We run about 500 DB per instance, and run at 20% of capacity (giving us enough power to boost).

Basically you answered my question, if we manage our workloads, we can expect no hard limits, we are getting a managed VM, with loose restrictions.

The use case is probably no different than what you have in Elastic Pools going up to 500+ DB per server.

Thanks!

[Mike-Ubezzi-MSFT]

@bootleg224 We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

[Mike-Ubezzi-MSFT]

@bootleg224 I am receiving conflicting information. It appears that the Azure SQL Database Managed Instance will throw some type of warning at 100 database, and prevent additional databases from being added to a single instance. Apologies for this inconstancy from what I communicated before.

[bootleg224]

Okay thanks, will check back in a few months to find out of the limit is changed

[ArtemRim]

Hi
The Azure SQL Database Managed Instance has limitation at 100 database. Is't actual information?
Was this limit change or not?
Because I have about 150 databases and for me the best solution is using he Azure SQL Database Managed, but this limit at 100 databases not allow me to use it.

[FasterDEV]

It's completely incomprehensible, I don't understand why there is such a soft limit for multitenant applications. We will probably have to migrate to another cloud, otherwise I don't know.