Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

SQLSaturday - divide and conquer - scale out using Azure federated databases

428 views

Published on

SQLSaturday Presentation on Scale out using Azure Federation Databases.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

SQLSaturday - divide and conquer - scale out using Azure federated databases

  1. 1. Martin Phelps Database Architect MiX telematics Divide and Conquer - Scale out using Federated Database in Azure
  2. 2. Intro  Scaling the database layer  Understanding of Sharding Basics  Demo  Performance  Limitations  Conclusions
  3. 3.  Scale OUT - Hardware  Scale UP  Master / Slave  Partitioned views  Table Partitioning  Windows Azure Sql Database Scaling the database layer
  4. 4.  Range Partitioning  List Partitioning  Hash Partitioning Sharding Basics – Types of sharding
  5. 5.  Problems it can address  Current Performance Issues  Physical hardware constraints  Logical constraints  Security (Separation of data)  Planning for future growth  Start Small  Grow on demand  Cater for high volume periods  Less surprises  Complex to Maintain  Schema maintenance  Monitoring of growth  Manual splitting of Shards - downtime Sharding Basics
  6. 6.  Editions  Web 100 Mb – 5 Gb  Business 10 Gb – 150 Gb  Premium – Dedicated Mem / CPU / IO  Developer Tools  Azure Console  Visual Studio  SSMS Azure – Sql Database
  7. 7. DEMO
  8. 8. Performance Florin Dumitrescu - http://www.ducons.com/blog/benchmarking- throughput-and-scalability-on-sql-azure-federations
  9. 9. Performance http://www.microsoft.com/casestudies/Windows-Azure/Flavorus/Ticketing-Company-Scales-to-Sell-150-000-Tickets-in-10-Seconds-by-Moving-to-Cloud-Computing-Solution/4000011072
  10. 10.  Merge Operations  Fan-out Queries  Schema Management  Policy based auto-repartitioning  Multi column federation keys  Data Sync Services  No Backup/Restore Operation Current Limitations
  11. 11.  Costs  Own Server + OS + Sql Ent (R75000 P/M)  Azure VM + OS + Sql Ent (36000 P/M)  Azure Sql Database (R27000 P/M)  Growth  Linear Scalability (Size & Performance)  Maturity  Been available for 2 years already  Continues to improve  Enterprise Ready?  Yes… But Conclusions
  12. 12.  http://www.ducons.com/blog/benchmarking-throughput-and-scalability-on-sql-azure- federations  http://research.microsoft.com/en-us/downloads/5c8189b9-53aa-4d6a-a086- 013d927e15a7/default.aspx  http://msdn.microsoft.com/en-us/library/ff394115.aspx  http://social.technet.microsoft.com/wiki/contents/articles/3507.windows-azure-sql- database-performance-and-elasticity-guide.aspx  http://msdn.microsoft.com/en-us/library/windowsazure/dn338083.aspx  http://research.microsoft.com/en-us/downloads/5c8189b9-53aa-4d6a-a086- 013d927e15a7/default.aspx  http://msdn.microsoft.com/en-us/magazine/hh848258.aspx  http://sqlazuremw.codeplex.com/releases/view/32334  http://sqlazurefedmw.codeplex.com/releases/view/71985 References
  13. 13. Q&A
  14. 14.  martin.phelps@gmail.com  za.linkedin.com/in/phelpsm  @mphelps_1968  www.databasediary.com Contact Me

×