Storage Options on Windows Azure
•Download as PPTX, PDF•
2 likes•782 views
Compare Storage options available on Windows azure. This presentation will compare SQL Azure, Table Storage and Document DB on azure.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Storage Options on Windows Azure
Similar to Storage Options on Windows Azure (20)
More from Himanshu Desai
More from Himanshu Desai (12)
Recently uploaded
Recently uploaded (20)
Storage Options on Windows Azure
- 1. Database options on Azure Himanshu Desai Principal Consultant, Technical Specialist (WCF) 1
- 2. Page Agenda › Understand Azure Database Offering › Overview of Azure SQL Database › Overview of Azure Table Storage › Overview of DocumentDB › Suitability of Each options / Copyright ©2014 by Readify Pty Ltd2
- 3. Page / Copyright ©2015 by Readify Pty Ltd4 DB SQL DB SQL DB SQL App SQL Azure DB Virtual Machine SQL Server Document DB Partition Key Partition 1 2 A Table Storage 1 A Row Key Entity
- 4. Page Who is responsible? › Developers › Testers › Operations / Copyright ©2014 by Readify Pty Ltd5
- 5. SQL Azure
- 6. Page Features › Databaseasaservice › ElasticScale withSharding* › Predicatableperformance › AvailabilitybackedbyreplicaandSLA › Dataprotectionviaauditing,restoreandgeo-replication › Selfmanaged › Threereplicaarerunningatonetime(oneprimaryandtwoormoreseconday) › Availabilityin3Tiers:Basic(2GB),Standard(250GB)&Premium(500GB) / Copyright ©2014 by Readify Pty Ltd7
- 7. Page Sharding – Why? › Thetotalamountofdataistoolargetofitwithintheconstraintsofasingledatabase › Thetransactionthroughputoftheoverallworkloadexceedsthecapabilitiesofasingle database › Tenantsmayrequirephysicalisolationfromeachother,soseparatedatabasesareneeded foreachtenant › Differentsectionsofadatabasemayneedtoresideindifferentgeographiesfor compliance,performanceorgeopoliticalreasons. / Copyright ©2014 by Readify Pty Ltd8
- 8. Page Horizontal Vs Vertical Scaling / Copyright ©2014 by Readify Pty Ltd9
- 9. Page Single Vs Multi-Tenant / Copyright ©2014 by Readify Pty Ltd10
- 10. Page Backup & Restore › Pointintimerestore › Geo-Restore › StandardGeo-replication › ActiveGeo-replication. / Copyright ©2014 by Readify Pty Ltd11
- 11. Page Management › SQLManagementStudio › RESTAPI’s › PowershellScripts › AzureManagementportal / Copyright ©2014 by Readify Pty Ltd12
- 12. Page What is not supported › https://msdn.microsoft.com/en-us/library/azure/ee336281.aspx / Copyright ©2014 by Readify Pty Ltd13
- 13. Page Demo / Copyright ©2014 by Readify Pty Ltd14
- 14. Page Azure Table Storage / Copyright ©2014 by Readify Pty Ltd15
- 15. Page What is Table Storage › Auto-sharded, key value store › Single table can contain upto 500TB at a cost of 7c/Gb/month › Scalability Target of 20K ops/second / Copyright ©2014 by Readify Pty Ltd16
- 16. Page Key Features › Schema less with only 3 predefined fields › Structured Storage › Massively scalable tables › Highly available and durable › Data is replicated several times › Usage via REST API or Windows Azure Storage client libraries › Storing data for efficient retrieval and presistence/ Copyright ©2014 by Readify Pty Ltd17
- 17. Page Required Entity Properties › PartitionKey & RowKey › Uniquely Identifies an entity › Defines the sort order › Use them to scale your app › Timestamp › Readonly › Optimistic concurrency / Copyright ©2014 by Readify Pty Ltd18
- 18. Page Table Storage Concepts / Copyright ©2014 by Readify Pty Ltd19 BooksOnline Users Books Email Name Email Name Title ISBN Title ISBN Accounts Tables Entities
- 19. Page Table Data Model › Table › A Storage account can create many tables › Table name is scoped by account › Set of entities (i.e. rows) › Entity › Set of properties (columns) › Required properties › PartitionKey, RowKey & Timestamp / Copyright ©2014 by Readify Pty Ltd20
- 20. PagePage / Copyright ©2014 by Readify Pty Ltd21 Partition Key 1 A Row Key Entity Partition: ABC / Machine 1 1 2 A Partition: DEF / Machine 2 1 2 A Partition : HIJ / Machine 3 1 2 A PartitionId RowKey Name Address Timestamp ABC 1 … ABC 2 …. ABC 3 …. PartitionId RowKey Name Address Timestam p DEF 4 DEF 5 DEF 6 PartitionId RowKe y Name Address Timestam p HIJ 7 HIJ 8 HIJ 9
- 21. Page PartitionKey and Partitions › PartitionKey › Used to group entities in the table into parititions › A table partition › All entities with same partition key value › Unit of scale › Control entity locality › Row key provides uniqueness within a partition / Copyright ©2014 by Readify Pty Ltd22
- 22. Page Partitioning Tables- Why › Scale › Eachindividualpartitionsaredistributedacrossmultiplestoragenodes › Systemmonitorsthepartitionsusageandautomaticallybalances partitionsacrossmultiple storagenodes › Apartitionsi.e.allentitieswithsamepartitionkey,willbeservedbya singlenode › Entitygrouptransactions › AllowtheapplicationtoautoperformmultipleCreate/Update/Delete operationsacrossmultipleentitiesusingbatchrequest / Copyright ©2014 by Readify Pty Ltd23
- 23. Page Query Speed › Fast › Singleparitionkeyandrowkeywithequality › Medium › Singlepartionbutasmallrangeofrowkey › Entirepartitionortablethatissmall › Slow › Largesinglescan › Largetablescan › “OR”predicatesonkeys=>noqueryoptimisation =>resultsinscan › ExpectContinuationtokens / Copyright ©2014 by Readify Pty Ltd24
- 24. Page Make Faster Queries › LargeScans › Splittherangeandparallelizequeries › Createandmaintainownviewsthathelpqueries › “Or”Predicates › Executeindividualqueryinparallel › UserInteractive › Cachetheresulttoreducescanfrequency / Copyright ©2014 by Readify Pty Ltd25
- 25. Page Continuation token › Maxof1krowsinaresponse › Attheendofpartitionrangeboundary › Maxof5secstoexecutethequery › Expectcontinuationtokenalways › Ifthequerytimesout,Serverreturnscontinuationtokensothatclient canmakeanotherquery › Whenthescancrossesthepartitionboundaries,continuatin tokenis returned. / Copyright ©2014 by Readify Pty Ltd26
- 26. Page Pagination › UseIQueryable<>.Take(N)tofetchthetopresults › Usecontinuation › http://<serviceUri>/Something?<originalQuery>&NextPartitionKey=< someValue>&NextRowKey=<someOtherValue> / Copyright ©2014 by Readify Pty Ltd27
- 27. Page Retrieve latest value › Have the row key as › DateTime.MaxValue.Ticks-DateTime.UtcNow.Ticks / Copyright ©2014 by Readify Pty Ltd28
- 28. Page Prefix based retrieval › Use CompareTo and ‘>’ and ‘<‘ function effectively › myTable.Partitionkey.CompareTo(“somekey”)>=0 / Copyright ©2014 by Readify Pty Ltd29
- 29. Page Demo / Copyright ©2014 by Readify Pty Ltd30
- 30. Page DocumentDB / Copyright ©2014 by Readify Pty Ltd31
- 31. Page What is DocumentDB? › Document database that supports fully manage storage of JSON documents in a highly performant way. › Fully managed distributed database. › (Still in preview and available in West US,North & West Europe, cost around 73 cents a day which includes 50% discount.) / Copyright ©2014 by Readify Pty Ltd32
- 32. Page Key Features › Schemaless,NoSQLdocumentdatabase › Fullymanaged,withprovisionedcapacity › AllowsforSQLlikequeriesonSemistructureddata(i.e.JSONfiles) › Supportsstrongconsistencyfortransactionalapplications › Designedtoscaleintopetabytes › Includeslibraries forNode,.NET, REST,Javascript(Client&Server),Python › IncludesHekatontechnologies(InMemorySQL) / Copyright ©2014 by Readify Pty Ltd33
- 33. Page Management › Supportedinnewportal › Managedatabaseaccount,collections,usersetc › Viewconsumptionstatistics › http://portal.azure.com › Usetoolslike › Queryexplorer › Documentexplorer › DocumentDBstudio / Copyright ©2014 by Readify Pty Ltd34
- 34. Page Overview of DocumentDB / Copyright ©2014 by Readify Pty Ltd35
- 35. Page Database Accounts / Copyright ©2014 by Readify Pty Ltd36
- 36. Page Resource Model › DatabaseAccount › Database › Collection › Document › Attachment › StoredProcedure › Trigger › User-definedfunctions › User › Permission › Media / Copyright ©2014 by Readify Pty Ltd37
- 37. Page Resource Addresssing › Restful › UniqueID › APIUrl: › https://{databaseaccount}.documents.azure.com › DocumentPath › /dbs/{database id}/colls/{collectionid}/docs/{documentid} › Clientlibraries › .NET › Javascript › Python/ Copyright ©2014 by Readify Pty Ltd38
- 38. Page Capacity Unit › Databaseaccountscomeswithadministrative quotaof › 100databases › 500,000users › 2,000,000permissions Itincludesquotaforcollections* IfyourunoutofCU,addmore.TheyarestackablebackedbySSD. EachCUcomeswith3elasticcollections,2000RU&10GBofSSD backeddocumentstorage › Elasticbydefault.Documentportionedbycollectioncanhaveunlimited storage.Notscopedtomachine.Actsasatransactiondomain / Copyright ©2014 by Readify Pty Ltd39
- 39. Page REST API › Standard Operations › Create,Delete,Put,Get,Post › Permanent Uri on Create › HMAC authentication using management or resource key › DocumentDB request headers / Copyright ©2014 by Readify Pty Ltd40
- 40. Page .NET Development › You need following from the portal after provision a database › Endpoint Url › Authorization key › Nu-get package › Install-Package Microsoft.Azure.Documents.Client – Pre › Use them to create DocumentClient / Copyright ©2014 by Readify Pty Ltd41
- 41. Page Demo / Copyright ©2014 by Readify Pty Ltd42
- 42. PagePage / Copyright ©2014 by Readify Pty Ltd43 Table Storage SQL Azure DocumentDB Semi-structured Fully Structured Semi-Structured Loosely typed Strongly typed Document Based Access Non-Relational (Not RDMS) Relational (RDMS) Non-Relational Massively scalable Highly Scalable Massively Scalable REST API & Client SDK for querying Full SQL Support Good SQL Support for querying hierarchical data within a collection N/A Stored Procs, UDFs etc Stored Procs, UDFs etc Each CU comes with 3 collections. In Preview, collection can grow upto 10GB and 2K RU of throughput.
- 43. Page Thank you Himanshu Desai Himanshu.desai@readify.net / Copyright ©2014 by Readify Pty Ltd44
Editor's Notes
- Standard Geo-Replication http://azure.microsoft.com/blog/2014/09/03/azure-sql-database-standard-geo-replication/ Point in Time restore http://azure.microsoft.com/blog/2014/10/01/azure-sql-database-point-in-time-restore/ Point-in-time restore Point-in-time restore is the most basic restore option, which you get automatically with basic, standard, and premium databases. You can use point-in-time restore to return your database to an earlier point in time. Go back 7 days with basic, 14 days with standard, and 35 days with premium. See Azure SQL Database Backup and Restore and Azure SQL Database Point in Time Restore (blog) for more information. Watch the video Restore a SQL Database Using Point in Time Restore to see how easy it is to use point-in-time restore. Geo-restore Geo-restore is similar to point-in-time restore. You also get it automatically with basic, standard, and premium databases. Geo-restore, however, is designed to be a basic recovery option when a database is unavailable because of a large scale incident or outage in the region where your database is hosted. The feature uses Azure read-access geo-redundant storage to store the most recent daily backup of your databases in a different geographical location. Consider geo-restore as a basic disaster recovery solution if your application can tolerate up to 24 hours downtime and data loss. For more information, read Azure SQL Database Geo-Restore (blog), and watch the video Restore a SQL Database Using Geo-Restore to see how to recover a database using geo-restore. Standard geo-replication Standard geo-replication is available for standard and premium databases. It’s designed for less write-intensive applications that nevertheless process high volumes of data and have more aggressive recovery requirements than geo-restore can offer. When the primary database fails, it shows as degraded, and you can initiate failover to a non-readable secondary database stored in a different region. For more information, see Standard Geo-Replication for Azure SQL Database and Azure SQL Database Standard Geo-Replication (blog), which has a thorough comparison of active geo-replication and standard geo-replication. Active geo-replication Active Geo-Replication is available for premium databases. It’s designed for write-intensive applications with the most aggressive recovery requirements. Using active geo-replication, you can create up to four readable secondaries on servers in different regions. These secondaries are maintained as continuous copies of the primary, and you can initiate failover to a secondary in the same way as standard geo-replication. Active geo-replication provides the highest degree of resiliency to temporary connection problems and high latency, so can support online application upgrade or relocation scenarios, as well as load balancing for read-only workloads. For more information, see Active Geo-Replication for Azure SQL Database and Spotlight on SQL Database Active Geo-Replication (blog). Additional business continuity features Database copy allows you to create a copy of a database either on the same or different servers in the same or different regions. The copy is transactionally consistent with the source when the database copy operation is complete. It is however a one-time copy, and not continuously replicated from the source. The feature can be used for data migration or ad hoc copy needs. For more information, see Copying Databases in Azure SQL Database. The import and export service lets you manually or automatically export a BACPAC file, which contains a logical copy of data and schema of a database, and then import the file to restore the database. Use import and export for Web and Business databases, which do not support other business continuity features. Or use it in addition to other business continuity features for long-term storage of daily backups or to retain backups beyond the retention period for point-in-time restore. For more information, see How to: Use the Import and Export Service in Azure SQL Database
- Standard Geo-Replication http://azure.microsoft.com/blog/2014/09/03/azure-sql-database-standard-geo-replication/ Point in Time restore http://azure.microsoft.com/blog/2014/10/01/azure-sql-database-point-in-time-restore/ Point-in-time restore Point-in-time restore is the most basic restore option, which you get automatically with basic, standard, and premium databases. You can use point-in-time restore to return your database to an earlier point in time. Go back 7 days with basic, 14 days with standard, and 35 days with premium. See Azure SQL Database Backup and Restore and Azure SQL Database Point in Time Restore (blog) for more information. Watch the video Restore a SQL Database Using Point in Time Restore to see how easy it is to use point-in-time restore. Geo-restore Geo-restore is similar to point-in-time restore. You also get it automatically with basic, standard, and premium databases. Geo-restore, however, is designed to be a basic recovery option when a database is unavailable because of a large scale incident or outage in the region where your database is hosted. The feature uses Azure read-access geo-redundant storage to store the most recent daily backup of your databases in a different geographical location. Consider geo-restore as a basic disaster recovery solution if your application can tolerate up to 24 hours downtime and data loss. For more information, read Azure SQL Database Geo-Restore (blog), and watch the video Restore a SQL Database Using Geo-Restore to see how to recover a database using geo-restore. Standard geo-replication Standard geo-replication is available for standard and premium databases. It’s designed for less write-intensive applications that nevertheless process high volumes of data and have more aggressive recovery requirements than geo-restore can offer. When the primary database fails, it shows as degraded, and you can initiate failover to a non-readable secondary database stored in a different region. For more information, see Standard Geo-Replication for Azure SQL Database and Azure SQL Database Standard Geo-Replication (blog), which has a thorough comparison of active geo-replication and standard geo-replication. Active geo-replication Active Geo-Replication is available for premium databases. It’s designed for write-intensive applications with the most aggressive recovery requirements. Using active geo-replication, you can create up to four readable secondaries on servers in different regions. These secondaries are maintained as continuous copies of the primary, and you can initiate failover to a secondary in the same way as standard geo-replication. Active geo-replication provides the highest degree of resiliency to temporary connection problems and high latency, so can support online application upgrade or relocation scenarios, as well as load balancing for read-only workloads. For more information, see Active Geo-Replication for Azure SQL Database and Spotlight on SQL Database Active Geo-Replication (blog). Additional business continuity features Database copy allows you to create a copy of a database either on the same or different servers in the same or different regions. The copy is transactionally consistent with the source when the database copy operation is complete. It is however a one-time copy, and not continuously replicated from the source. The feature can be used for data migration or ad hoc copy needs. For more information, see Copying Databases in Azure SQL Database. The import and export service lets you manually or automatically export a BACPAC file, which contains a logical copy of data and schema of a database, and then import the file to restore the database. Use import and export for Web and Business databases, which do not support other business continuity features. Or use it in addition to other business continuity features for long-term storage of daily backups or to retain backups beyond the retention period for point-in-time restore. For more information, see How to: Use the Import and Export Service in Azure SQL Database
- Standard Geo-Replication http://azure.microsoft.com/blog/2014/09/03/azure-sql-database-standard-geo-replication/ Point in Time restore http://azure.microsoft.com/blog/2014/10/01/azure-sql-database-point-in-time-restore/ Point-in-time restore Point-in-time restore is the most basic restore option, which you get automatically with basic, standard, and premium databases. You can use point-in-time restore to return your database to an earlier point in time. Go back 7 days with basic, 14 days with standard, and 35 days with premium. See Azure SQL Database Backup and Restore and Azure SQL Database Point in Time Restore (blog) for more information. Watch the video Restore a SQL Database Using Point in Time Restore to see how easy it is to use point-in-time restore. Geo-restore Geo-restore is similar to point-in-time restore. You also get it automatically with basic, standard, and premium databases. Geo-restore, however, is designed to be a basic recovery option when a database is unavailable because of a large scale incident or outage in the region where your database is hosted. The feature uses Azure read-access geo-redundant storage to store the most recent daily backup of your databases in a different geographical location. Consider geo-restore as a basic disaster recovery solution if your application can tolerate up to 24 hours downtime and data loss. For more information, read Azure SQL Database Geo-Restore (blog), and watch the video Restore a SQL Database Using Geo-Restore to see how to recover a database using geo-restore. Standard geo-replication Standard geo-replication is available for standard and premium databases. It’s designed for less write-intensive applications that nevertheless process high volumes of data and have more aggressive recovery requirements than geo-restore can offer. When the primary database fails, it shows as degraded, and you can initiate failover to a non-readable secondary database stored in a different region. For more information, see Standard Geo-Replication for Azure SQL Database and Azure SQL Database Standard Geo-Replication (blog), which has a thorough comparison of active geo-replication and standard geo-replication. Active geo-replication Active Geo-Replication is available for premium databases. It’s designed for write-intensive applications with the most aggressive recovery requirements. Using active geo-replication, you can create up to four readable secondaries on servers in different regions. These secondaries are maintained as continuous copies of the primary, and you can initiate failover to a secondary in the same way as standard geo-replication. Active geo-replication provides the highest degree of resiliency to temporary connection problems and high latency, so can support online application upgrade or relocation scenarios, as well as load balancing for read-only workloads. For more information, see Active Geo-Replication for Azure SQL Database and Spotlight on SQL Database Active Geo-Replication (blog). Additional business continuity features Database copy allows you to create a copy of a database either on the same or different servers in the same or different regions. The copy is transactionally consistent with the source when the database copy operation is complete. It is however a one-time copy, and not continuously replicated from the source. The feature can be used for data migration or ad hoc copy needs. For more information, see Copying Databases in Azure SQL Database. The import and export service lets you manually or automatically export a BACPAC file, which contains a logical copy of data and schema of a database, and then import the file to restore the database. Use import and export for Web and Business databases, which do not support other business continuity features. Or use it in addition to other business continuity features for long-term storage of daily backups or to retain backups beyond the retention period for point-in-time restore. For more information, see How to: Use the Import and Export Service in Azure SQL Database
- http://blogs.msdn.com/b/windowsazurestorage/archive/2012/11/06/windows-azure-storage-client-library-2-0-tables-deep-dive.aspx
- In Preview, collections quota can be between 0-10GB http://azure.microsoft.com/en-us/documentation/articles/documentdb-manage/ CU: Measure of Provisioned Storage(GB) and Throughput (Req/s)