Hello everyone; This is my first post on asp.net web forums. I am hoping to get a little advice architecturally for a hosted solution that already exists. Right now I am already using the sqlmembership provider right out of the box. Here is an explanation of my current state:
I have an asp.net 4.0 application that uses an SQL Express 2008 database backend. This database includes the sqlmembership provider schema as well as my custom application schema. The application works great right now as I only have 1 client. This application is hosted with a web hosting company.
Now, I am starting to get more and more clients, and especially more and more clients that do not have the IT infrastructure to host their own copy of hte application, I need to have the ability to host multiple instances with one hosting company.
This is where I am looking for some advice.....
This is what I am planning to do:
Move the sqlmembership schema to a "control database ...
Go to the complete details ...