Each tenant has its own database

If it weren’t for the graphic, I would suggest this was a typo. I’m not aware this is possible, but I believe it could be. If it is, it’s very uncommon. You may need to contact Acumatica support directly.

Hello ​@davetaylorcat as per my research : the documentation is technically correct but poorly worded. You cannot achieve "one instance, one URL, multiple databases" - that configuration doesn't exist in Acumatica. You need separate instances for separate databases, which means separate URLs/virtual directories.

You may check post for clarification:
 

hope it hepls.

​@darylbowman and ​@Abhishek Niikam Thank you both for your quick responses. I feared that the single instance single database was the official configuration. Pretty much everything else I have found proved that out except for that one sentence in the documentation. Being new to the Acumatica space and coming from other ERP packages, having this community as a resource is a great help.

Again, I appreciate your help with my topic.

​@davetaylorcat !--startfragment>

To clarify for everyone checking this post:
An Acumatica instance and its tenants share the same database. If the policy requires separate databases, then each company must have its own dedicated Acumatica instance.

!--endfragment>

As the third person essentially saying the same thing, I don't think this clarifies anything unless you have a solid source indicating Acumatica definitely does not support a multi-tenant instance that doesn't share a database, especially since the documentation from Acumatica indicates they do.

Can you provide one?

Hi ​@davetaylorcat 

 

In Acumatica, an application instance is tied to a single MS SQL database. Multiple tenants exist inside that one database and are separated logically, not physically.

The statement in the documentation means that in an architecture with multiple application instances, each instance can have its own database, and each instance can contain multiple tenants. It does not mean that tenants within the same instance can each be placed in separate SQL databases.

If you need complete physical isolation at the database level (for example, Company A in DBA and Company B in DBB), you must create separate Acumatica application instances, each connected to its own SQL database.

So the desired configuration is achieved by:
– Creating Instance A connected to database DBA (with its tenant or tenants)
– Creating Instance B connected to database DBB (with its tenant or tenants)

It is not possible to have multiple tenants within a single Acumatica instance each mapped to different SQL databases.

Hii  ​@davetaylorcat,

According to my knowledge, one Acumatica application instance connects to only one SQL database. Multiple tenants can exist, but they are logically separated within the same physical database.

If complete physical database isolation is required (for example, Company A in DBA and Company B in DBB), the supported approach is to deploy separate Acumatica application instances, each connected to its own database.

A single instance cannot map different tenants to separate SQL databases.

Hi ​@davetaylorcat ,

Acumatica does not support the configuration you have described. You can’t map different tenants to separate SQL databases. If you want to have a separate database per tenant you should use separate Acumatica instances.

Hi ​@davetaylorcat,

In Acumatica single instance connecting to multiple databases is not possible, even when you have multiple tenants. I guess there is an obvious reason due to maintenance, backups, etc. Since, it is always one instance points to a single database in Web.config, you cannot have multiple connection strings in there.

I am still not sure what is the actual business scenario. However, you can use a Restriction groups and various user/role/screen/field level permission to handle a situation where data is visible to certain users, etc.

You can refer to below links for more information on Restriction groups. Hope this is helpful.

Restriction Groups in Acumatica ERP