title: Multi-tenancy query execution speed: shared-schema with partitioning vs. seperate-schema
body: <p>I've been reading through the excellent <a href="https://msdn.microsoft.com/en-us/library/hh534476.aspx" rel="nofollow">Developing Multi-tenant Applications for the Cloud, 3rd Edition</a> and am trying to understand how partitioning impacts on query performance in Windows Azure SQL Database.</p>
  
  <p>If you use the shared schema approach and put all tenants records in a single table and separate their data using partitions, is that always going to be slower than a separate schema approach due to the larger number of records in the table, or does the partitioning effectively make each partition act like its own table?</p>
  
  <p>(I appreciate query execution speed is only one of many factors to consider when choosing a multi tenancy strategy, we're not basing our decisions on performance alone.)</p>