Forums

Thanks for the reply. I understand the concern about hacking.

With our SurPaaS archetecture, we use the subdomain name to look up in tables we maintain that point to the proper database, which may or may not = the actual name of the DB.

For our SaaS customers, we use wildcard subdomain so that the users have a simple, contextual url by which to access their application.

https://tenantname/company.com is easy to remember. IT is true, if the tenant name is known, others can access the logon. That is why we set the default password to "must change"

What we are doing now with your method:
In the Spendid_hosting_sites view, we are setting "Connection_String" Initial Catalog with "tenantname", same as the end-user url subdomain. This works fine.

I would like to just skip the step of creating an IIS host for each tenant, and maintain another table.

Accepting all the disclaimers, I would like to add another factory that declares the subdomain as the database name as an option. I am looking for the best way to do this without changing too much SplendidCRM code.

We don't use the hosting database solution with our Azure system. Instead, we have created SplendidCRM Ultimate Edition to dynamically create new VM and SQL instances for each customer.

I'm not sure why you would have a problem connecting to 2 separate databases inside an Azure VM. I would expect the problems you are having to do with the fierwalls being used by SQL Azure.

.NET System.Data.SqlClient object should be able to connect to any number of separate databases. I would suggest that you use PowerShell to test connections to the various databases.