title: Azure SQL: Performance benchmarks between S0, S1, S2 tier and P1, P2, P3 Tiers?
body: <p>We have a few legacy databases in the Auzre cloud that are in the older pricing tiers ('Business' - before the Basic / Standard / Premium tiers became available).</p>
  
  <p>We are looking to do a transition over to the new structures (and take advantage of the new features) - and as a result ran a few tests come to an understanding of how much of a  performance increase we would get for the pricing structures.</p>
  
  <p>The Azure SQL versions are measured in Database Throughput Units (DTUs), and Azure attributes these units directly to increases in performance:
  <em>A DTU represents the power of the database engine as a blended measure of CPU, memory, and read and write rates. This measure helps a customer assess the relative power of the six SQL Database performance levels available across Basic, Standard and Premium (Basic, S1, S2, P1, P2, and P3). Please visit the performance guide on MSDN for more information.</em></p>
  
  <p>After not seeing any difference between an S0 and S2 database - we stood up a P3 version to test as a benchmark against the S0.  We were surprised to find absolutely no performance difference between running a fairly complex query against the S0 and P3 Azure SQL databases.</p>
  
  <p>Both instances were build from a backup file from the original Business tier Azure SQL file (Could this be an issue?)</p>
  
  <p>I am at a loss - as I expected that the P3 database (800 DTU units) was going to blow away the S0 database (10 DTU units).  Both performed almost identically.  Both also used the same execution plan, and both had the indexes in place (DBA set those up - not myself). </p>
  
  <p>Any insights as to why we would have not seen a difference in these configurations?</p>
  
  <p>Anyone else have any examples of increased performance or performance distinctions across these tiers? </p>