title: Which Multi-tenant approach is recommended with SQL Server 2008
body: <p>I have to use ASP.NET MVC 3 or above and SQL Server 2008. As per <a href="http://msdn.microsoft.com/en-us/library/aa479086.aspx" rel="nofollow">Multi-Tenant Data Architecture</a> post, there are 3 ways to implement multi-tenancy</p>
  
  <ol>
  <li><p>Separate Databases</p></li>
  <li><p>Shared Database, Separate Schemas</p></li>
  <li><p>Shared Database, Shared Schema</p></li>
  </ol>
  
  <p>I have following details:</p>
  
  <ol>
  <li>User should be able to backup and restore their data.</li>
  <li>No of tenants : 1000 (approx)</li>
  <li>Each tenant might belong to different domain(url).</li>
  <li>It must support monitoring and management of tenants.</li>
  <li>It must support user authentication and authorization for each tenant</li>
  <li>It must support tenant customization(enable disable features set)</li>
  <li>No of tables in each tenant: 100 (initial) </li>
  </ol>
  
  <p>I would like to know what your experience says about which approach is more suitable for the project considering Economic and Security? Is there any good real time example(open source project) similar to this? I can use one dedicated server for the project. </p>