I am in the process of converting a single SQL DB website (ASP.NET / VB.Net) into a multitant app, Where each customer has their own database.
In the old site, all ASP roles, logins and providers point to a single database.
Now we have many databases, I am wondering what will happen to use the best architecture / techniques.
Should we all subscribe & amp; Role content in a single database that configures tenants or we have a subscription and amp; Roles in each individual tenants database? Option 2 seems hard because I think that ASP.net only likes a group of RoleProviders defined in web.config.
Did anyone try this before or any recommendations?
If you are using the ASP.NET subscription model with built-in providers, then in a DB The easiest to insert is as you indicate.
One option, and I did not try it, define in my web. Configes file a provider for each tenant. This will allow each tenant to have their membership dB and you allow tenants to avoid the name of the user (if this is a requirement).
Comments
Post a Comment