Business Central (and way back to Navision) stores all tables for all ERP companies in the one database and in the one schema (dbo). So, if you have (say) 18 companies and each has 3.6K tables, suddenly you have 66K tables all in the dbo schema in one database.
This is a nuisance for tools that use catalogue discovery - such as a plethora of ELT tools - because it's too easy to time out or to hit capacity limits due to the sheer volume of tables, even if most of them will be ignored (because they are CRONUS, or whatever).
It would be much nicer if instead of tables being
database.dbo.company$table$extensionGUID
they were
database.company.table$extensionGUID
Imagine having companies as schemas, and fewer (way fewer) tables per schema in the database? It would be wonderful for those doing database work.
Thank you.
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team