title: Converting Single DB ASP.NET Site into MultiTenant - Membership and Roles Dilemma
body: <p>I'm in the process up changing a single SQL DB website (ASP.NET/VB.NET) into a multitenant app, where each client has their own database.</p>
  
  <p>In the old site, all the ASP roles, logins and providers pointed to the single database.</p>
  
  <p>Now we have multiple databases, I'm wondering what would the best architecture/techniques to use. There is one database that configures the tenants, such as the company name, various settings (that would normally be in a web.config) and the connection string to their tenant database.</p>
  
  <p>Should we have all the membership &amp; role stuff in the single database that configures the tenants  or do we have membership &amp; roles in each individual tenants database? Option 2 seems tricky because I think ASP.NET only likes one set of RoleProviders defined in the web.config.</p>
  
  <p>Has anyone tried this before or got any recommendations?</p>