title: Multi Tenant Data Architecture in Azure
body: <p>I want to implement multi tenant architecture for database. Plan is to have same database but have schema in it which will have same tables, sprocs, triggers, etc. repeated for each tenant. Tenant will be mapped to a schema and adding a tenant is like adding a schema. </p>
  
  <p>And depending on the sub-domain, i will figure out the tenant and pull / push information to the respective database schema. </p>
  
  <p>However, while looking for the way to implement the same i came across many articles and blogs and am confuse whether the word 'schema' is right in my context or should i go for Federation? And if i have to go to federation - does it mean that each tenant will be a federated member which will be mapped to a schema?</p>
  
  <p>Can someone throw some more light on it?</p>