SCALE ON DEMANDCLOUD ON YOUR TERMS
THE FANTASTIC 12 OF 2012        1         2        3    4        5         6        7    8        9        10        11   12
BETTER SCALINGWINDOWS SERVER 2012                           16x                            increase High capacity virtual ...
BETTER SCALING WITH WINDOWS SERVERTECHNICAL BENEFITSHigh capacity virtual processor & memoryAllows SQL Server VM to use up...
BETTER PERFORMANCEWINDOWS SERVER 2012                           Support for                            640                ...
BETTER PERFORMANCE WITH WINDOWS SERVERTECHNICAL BENEFITS
BETTER STORAGE SUPPORTWINDOWS SERVER 2012                  Increase storage by                            30-             ...
BETTER STORAGE SUPPORT WITH WINDOWS SERVERTECHNICAL BENEFITS
BETTER NETWORKINGWINDOWS SERVER 2012                               Reduce                       operating costs   QoS – Ne...
BETTER NETWORKING WITH WINDOWS SERVERTECHNICAL BENEFITS
ENTERPRISE CHALLENGES DRIVING HYBRID IT
WHY MICROSOFT FOR YOUR HYBRID IT?
Business Challenge   SolutionKey Benefits
Business Challenge   SolutionKey Benefits
BENEFITS OF OPTIMIZING SQL SERVER FOR PRIVATECLOUD
SCENARIOS
Windows Azure SQL Database   DEVELOP NEW CLOUD-DESIGNED APPS                         SQL Database                Mobile   ...
Windows Azure SQL Database   DEVELOP NEW CLOUD-DESIGNED APPS
Windows Azure SQL Database   EXTEND ON-PREMISE APPS TO SQL DATABASE                SERVICE
Windows Azure SQL Database                EXTEND ON-PREMISE APPS TO SQL                DATABASE SERVICE
WINDOWS AZURE SQL DATABASE -CONSIDERATIONS FOR DEVELOPERSConnectionsDatabasesSystem databases - master & tempdbUser databa...
WINDOWS AZURE SQL DATABASE - CONNECTIONSServer name is logicalObtained from Azure subscriptionConnection is routed to a no...
WINDOWS AZURE SQL DATABASE - DRIVERSCurrentSQL Server 2008 ODBC Driver or laterSQL Server 2008 Driver for PHP 1.1 or later...
WINDOWS AZURE SQL DATABASE – MASTERDATABASEOne master database per logical serverNew dbmanager and loginmanager rolesOnly ...
WINDOWS AZURE SQL DATABASE – MASTERDATABASEGateway processed statementsCreate/alter/drop databaseCreate/alter/drop loginCr...
WINDOWS AZURE SQL DATABASE – TEMPDBDATABASETempdb is available logicallyTempdb cannot be referenced directlyIn object Iden...
WINDOWS AZURE SQL DATABASE – USERDATABASESUser databases can only be created in masterFile placement is not allowed. Stora...
WINDOWS AZURE SQL DATABASE – SECURITYLogical ServerNo sysadmin or sa privilegeAuthenticationOnly SQL Logins supportedMaste...
WINDOWS AZURE SQL DATABASE –PROGRAMMABILITYInstance & Metadata collationFixed to SQL_Latin1_General_100_CI_ASTempdb collat...
HIGH AVAILABILITY FOR SQL DATABASESReads are completed at the primaryWrites are replicated to secondariesEach replica is b...
CUSTOMER BENEFITS OF HIGH AVAILABILITYNo additional administration costACID properties are maintained by the systemFailove...
DATABASE COPYExtends replica creation and expose to userTransactional consistency after completionCan copy to any server i...
USING AZURE STORAGE AUTOMATIC GEO-REDUNDANCYNo extra cost for geo-replicationSame backup process/restore process + failove...
INTRODUCING SCALE OUT FEDERATIONSCanonical 3 tier app scales by adding andremoving nodesFederations extend the model to th...
INTRODUCING SCALE OUT FEDERATIONSCanonical 3 tier app scales by adding andremoving nodesFederations extend the model to th...
WHY USE FEDERATIONS?Go Beyond Single DB to Practically Unlimited Scale:Harness 100s of Azure SQL Database nodesBest Econom...
OVERVIEW - CONCEPTS                                   AU               AU                AU                               ...
OVERVIEW – ARCHITECTURERepartitioning Operations without Downtime!SPLIT members to spread workloads over to more nodesDROP...
OVERVIEW – ARCHITECTURE (CONTINUED)Built-in Data-Dependent RoutingDDR ensure app can discover where the data is just-in-ti...
SCHEMA MODEL FOR FEDERATIONSFederated Databases have a distributed schema model:Federated TablesReference TablesCentral Ta...
WHAT IS A SCALE-FIRST DESIGN?What is a Scale-first DB Design Approach?Design principles such as normalization model data f...
PICKING TABLE GROUPSDefine Table Groups“Table Groups” are properties of the same entity - tied with fk relationships oracc...
PICKING FEDERATIONSPick Federations – 1 or more “Table Groups” that needscale-out“Table Groups” may need scale out if they...
PICKING FEDERATION KEYSPick Federation Keys and Define the Atomic Units (AU)*AU instance is the target of in all (or most)...
CONSIDERATIONS FOR REFERENCE DATAWhat are Reference Tables?Look up tables that are cloned to all membersProvide easier pro...
CENTRAL TABLESCentral TablesTables in table-groups that are not scale-out: Heavily cached & low traffic dataNo schema chan...
FEDERATED AND REFERENCE TABLESReference TablesOptimize lookups for queries in federationsNo schema changes required,Placed...
FEDERATED AND REFERENCE TABLES
HOW ABOUT OBJECTS OTHER THAN TABLES?Deployed along with the table-groupsObject with local tablegroup dependencies: deploye...
TIP: AUTO-MAINTAIN FEDERATION COLUMNSfederation_filtering_value(id)Returns the filtering value used for your connectionAdd...
TIP: OPTIMISTIC CONCURRENCYHow to manage optimistic concurrency without timestamppropertyTimestamp type is not allowed on ...
ADDITIONAL RESOURCES
NEXT STEPS
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be...
Sql server 2012_sp1_06_of_12_scale_on_demand_level300_dark_deck
Sql server 2012_sp1_06_of_12_scale_on_demand_level300_dark_deck
Sql server 2012_sp1_06_of_12_scale_on_demand_level300_dark_deck
Sql server 2012_sp1_06_of_12_scale_on_demand_level300_dark_deck
Sql server 2012_sp1_06_of_12_scale_on_demand_level300_dark_deck
Sql server 2012_sp1_06_of_12_scale_on_demand_level300_dark_deck
Sql server 2012_sp1_06_of_12_scale_on_demand_level300_dark_deck
Sql server 2012_sp1_06_of_12_scale_on_demand_level300_dark_deck
Sql server 2012_sp1_06_of_12_scale_on_demand_level300_dark_deck
Sql server 2012_sp1_06_of_12_scale_on_demand_level300_dark_deck
Sql server 2012_sp1_06_of_12_scale_on_demand_level300_dark_deck
Sql server 2012_sp1_06_of_12_scale_on_demand_level300_dark_deck
Upcoming SlideShare
Loading in...5
×

Sql server 2012_sp1_06_of_12_scale_on_demand_level300_dark_deck

137

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
137
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Sql server 2012_sp1_06_of_12_scale_on_demand_level300_dark_deck

  1. 1. SCALE ON DEMANDCLOUD ON YOUR TERMS
  2. 2. THE FANTASTIC 12 OF 2012 1 2 3 4 5 6 7 8 9 10 11 12
  3. 3. BETTER SCALINGWINDOWS SERVER 2012 16x increase High capacity virtual processor & memory Increased VM densityHigh capacity logical processor & memory Increased cluster scalability
  4. 4. BETTER SCALING WITH WINDOWS SERVERTECHNICAL BENEFITSHigh capacity virtual processor & memoryAllows SQL Server VM to use up to 64 virtual processors and 1TB of memoryIncreased VM density› Up to 8,000 SQL Server VMs per cluster› Support for up to 320 logical processors and 4 TB memoryHigh capacity logical processor & memoryAllows SQL Server to use up to 640 logical processors& 4 TB of memoryIncreased cluster scalabilitySupports SQL Server clusters up to 64 nodes
  5. 5. BETTER PERFORMANCEWINDOWS SERVER 2012 Support for 640 processers & 4TB of RAM Support for NUMA in Hyper-V Fiber Channel Support in Hyper-V New VHDX Format
  6. 6. BETTER PERFORMANCE WITH WINDOWS SERVERTECHNICAL BENEFITS
  7. 7. BETTER STORAGE SUPPORTWINDOWS SERVER 2012 Increase storage by 30- 90% SMB Support 4-KB Disk Sectors Storage Spaces Data Deduplication
  8. 8. BETTER STORAGE SUPPORT WITH WINDOWS SERVERTECHNICAL BENEFITS
  9. 9. BETTER NETWORKINGWINDOWS SERVER 2012 Reduce operating costs QoS – Network Bandwidth Enforcing Extensible Switch & Network Virtualization Windows NIC Teaming
  10. 10. BETTER NETWORKING WITH WINDOWS SERVERTECHNICAL BENEFITS
  11. 11. ENTERPRISE CHALLENGES DRIVING HYBRID IT
  12. 12. WHY MICROSOFT FOR YOUR HYBRID IT?
  13. 13. Business Challenge SolutionKey Benefits
  14. 14. Business Challenge SolutionKey Benefits
  15. 15. BENEFITS OF OPTIMIZING SQL SERVER FOR PRIVATECLOUD
  16. 16. SCENARIOS
  17. 17. Windows Azure SQL Database DEVELOP NEW CLOUD-DESIGNED APPS SQL Database Mobile Web
  18. 18. Windows Azure SQL Database DEVELOP NEW CLOUD-DESIGNED APPS
  19. 19. Windows Azure SQL Database EXTEND ON-PREMISE APPS TO SQL DATABASE SERVICE
  20. 20. Windows Azure SQL Database EXTEND ON-PREMISE APPS TO SQL DATABASE SERVICE
  21. 21. WINDOWS AZURE SQL DATABASE -CONSIDERATIONS FOR DEVELOPERSConnectionsDatabasesSystem databases - master & tempdbUser databasesSecurityProgrammability
  22. 22. WINDOWS AZURE SQL DATABASE - CONNECTIONSServer name is logicalObtained from Azure subscriptionConnection is routed to a node / databaseLogically scoped to the databaseYou cannot transition from one database to anotherOnly TCP/IP protocol availableNew firewall to enable connectivity
  23. 23. WINDOWS AZURE SQL DATABASE - DRIVERSCurrentSQL Server 2008 ODBC Driver or laterSQL Server 2008 Driver for PHP 1.1 or laterSQL Server JDBC Driver 3.0SqlClient from .NET 3.5 SP1 or laterUpcomingSQL Server ODBC Driver for LinuxSQL Server OLEDB Provider
  24. 24. WINDOWS AZURE SQL DATABASE – MASTERDATABASEOne master database per logical serverNew dbmanager and loginmanager rolesOnly some user objects can be createdDatabases, logins & usersPermission controlled by role membershipSystem owns master databaseNo dbo privilege to end-userUsed only for creating instance-level entitiesStores Azure specific metadata like firewall rules, billing etc.
  25. 25. WINDOWS AZURE SQL DATABASE – MASTERDATABASEGateway processed statementsCreate/alter/drop databaseCreate/alter/drop loginCreate/alter/drop federationUse federationImpact on scriptsCannot be mixed with other T-SQL statements in a batch!Session settings like PARSEONLY doesn’t affect execution
  26. 26. WINDOWS AZURE SQL DATABASE – TEMPDBDATABASETempdb is available logicallyTempdb cannot be referenced directlyIn object IdentifiersUSE statementSupported objectsLocal temporary tables / stored proceduresTable variables
  27. 27. WINDOWS AZURE SQL DATABASE – USERDATABASESUser databases can only be created in masterFile placement is not allowed. Storage managed by the systemConnections are made to database explicitlyCannot use USE <dbname> to switch contextSupported ALTER DATABASE OptionsCOLLATION, RECURSIVE_TRIGGERSFixed Database OptionsCOMPATIBILITY_LEVEL is set to 100READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION are set to ONCannot reference otherdatabases
  28. 28. WINDOWS AZURE SQL DATABASE – SECURITYLogical ServerNo sysadmin or sa privilegeAuthenticationOnly SQL Logins supportedMaster databaseNo dbo or db_owner privilegePermissions granted via dbmanager & loginmanager roles onlyUser databasesEnd-user has full controlPermissions can be managed as usual
  29. 29. WINDOWS AZURE SQL DATABASE –PROGRAMMABILITYInstance & Metadata collationFixed to SQL_Latin1_General_100_CI_ASTempdb collation is also sameIdentifiers & variables are always case-insensitiveFeature restrictionsClustered index required on all tablesFeatures/constructs with physical attributes not available or restrictedMost backward compatible or deprecated features are not availableDMVs/DMFs are database-scoped
  30. 30. HIGH AVAILABILITY FOR SQL DATABASESReads are completed at the primaryWrites are replicated to secondariesEach replica is backed up independently toattached storage
  31. 31. CUSTOMER BENEFITS OF HIGH AVAILABILITYNo additional administration costACID properties are maintained by the systemFailovers are fully automatedDynamic routing of connectionsNo additional charges for database redundancyTarget RPO=0, RTO=30sec99.9% availability SLA
  32. 32. DATABASE COPYExtends replica creation and expose to userTransactional consistency after completionCan copy to any server in the same regionCan copy from live databaseCan cancel in flight operationCan monitor statusOnly billed if copy is successfulFamiliar T-SQL interfaceCREATE DATABASE db2 AS COPY OF[source_server_name.] db1
  33. 33. USING AZURE STORAGE AUTOMATIC GEO-REDUNDANCYNo extra cost for geo-replicationSame backup process/restore process + failoverNot suitable for mission critical applicationsHigh RPO = export interval (potentially shorter)High RTO = Azure storage RT (~24 hrs) + time to import + time to start app +DNS change
  34. 34. INTRODUCING SCALE OUT FEDERATIONSCanonical 3 tier app scales by adding andremoving nodesFederations extend the model to the DB TierAdd and Remove Azure SQL Database nodes with federations.Scale on demand to your traffic without any downtime!
  35. 35. INTRODUCING SCALE OUT FEDERATIONSCanonical 3 tier app scales by adding andremoving nodesFederations extend the model to the DB TierAdd and Remove Azure SQL Database nodes with federations.Scale on demand to your traffic without any downtime!
  36. 36. WHY USE FEDERATIONS?Go Beyond Single DB to Practically Unlimited Scale:Harness 100s of Azure SQL Database nodesBest EconomicsElastic database tier that can repartition with your applications workload. No downtime required!Simplified Multi-tenancy:Efficient management of tenant placement and re-placementSimplified Development and Administration:Robust programming & connectivity model with native tooling
  37. 37. OVERVIEW - CONCEPTS AU AU AU PK=5 PK=25 PK=35 AU AU AU PK=5 PK=25 PK=35 Orders_federation Orders_federation AU AU AU PK=1005 PK=1025 PK=1035 fed_name
  38. 38. OVERVIEW – ARCHITECTURERepartitioning Operations without Downtime!SPLIT members to spread workloads over to more nodesDROP members to shrink back to fewer nodes Orders_federation Orders_federation Orders_Fed [5000, 7500) & [7500, 10000) [5000, 10000)
  39. 39. OVERVIEW – ARCHITECTURE (CONTINUED)Built-in Data-Dependent RoutingDDR ensure app can discover where the data is just-in-timeApps no longer has to cache ‘shard map’No cache coherency issues even with repartitioningPrevents connection pool fragmentation issues Orders_federation Orders_federation Orders_Fed
  40. 40. SCHEMA MODEL FOR FEDERATIONSFederated Databases have a distributed schema model:Federated TablesReference TablesCentral Tables Orders_federation Orders_federation fed_name
  41. 41. WHAT IS A SCALE-FIRST DESIGN?What is a Scale-first DB Design Approach?Design principles such as normalization model data for high consistency. You can applyadditional compromises to your design to gain scalability. Scale-first database designconsiders scale as the top concern of your design and applies these additional scalabilityconstraints to your data model and database design.Step by step… Normalized to Scale-FirstNormalize your data model all the way and then…1. Apply Scale-first data model considerations2. Generate Schema with Scale-first annotations Orders_federation Orders_federation fed_name
  42. 42. PICKING TABLE GROUPSDefine Table Groups“Table Groups” are properties of the same entity - tied with fk relationships oraccess patternsEx: Customer entity may have customers, customer_address, customer_category tables.Order entity may be made up of orders and order_details tables etc. Orders_federation Orders_federation fed_name
  43. 43. PICKING FEDERATIONSPick Federations – 1 or more “Table Groups” that needscale-out“Table Groups” may need scale out if they have high storage needs orcomputational capacity needs.Ex: Customer and order table groups can be scaled out in customer_orders_fedfederation Orders_federation Orders_federation fed_name
  44. 44. PICKING FEDERATION KEYSPick Federation Keys and Define the Atomic Units (AU)*AU instance is the target of in all (or most) latency and scale sensitive queriesAU instance is target of all (or most) transaction boundariesAUs distribute the app workload equally to all membersLargest AU instance fits in the scale-up limit of SQL Database*AU is an instance of a federation key – ex: all data in the table-group that belongs to customerid=55 would be the AU for federation key on customerid. Orders_federation Orders_federation fed_name
  45. 45. CONSIDERATIONS FOR REFERENCE DATAWhat are Reference Tables?Look up tables that are cloned to all membersProvide easier programmabilityEasier queries & transactionsLowered latencies with local joinsHow to pick ref tables?Set of tables use for lookups in in latency & scale sensitive workload of the appTables that don’t need strict consistency – (o.k with eventual consistency)Tip: Syncing ref tables will be possible with data syncservice in future…
  46. 46. CENTRAL TABLESCentral TablesTables in table-groups that are not scale-out: Heavily cached & low traffic dataNo schema changes required. Simply left in root Orders_federation Orders_federation fed_name
  47. 47. FEDERATED AND REFERENCE TABLESReference TablesOptimize lookups for queries in federationsNo schema changes required,Placed in federation membersFederated TablesDistributed tables across federationsHas to contain federation key as part of the tableDistribution column comply with the datatype of the federationHas to be annotated with “FEDERATE ON” clausePlaced in federation members Orders_federation Orders_federation fed_name
  48. 48. FEDERATED AND REFERENCE TABLES
  49. 49. HOW ABOUT OBJECTS OTHER THAN TABLES?Deployed along with the table-groupsObject with local tablegroup dependencies: deployed long with thetable-groupsObjects with none-local dependencies: need to be implemented at theapp level Orders_federation Orders_federation fed_name
  50. 50. TIP: AUTO-MAINTAIN FEDERATION COLUMNSfederation_filtering_value(id)Returns the filtering value used for your connectionAdd this default for auto-maintaining the federation columns
  51. 51. TIP: OPTIMISTIC CONCURRENCYHow to manage optimistic concurrency without timestamppropertyTimestamp type is not allowed on Federated TablesTimestamp Generation can be expensive for large scale appsProvides linearly increasing values global to the dbCan only be generated at the db tierBenefits of Datetime2Does not require centralized timestamp generationHas 100ns accuracy
  52. 52. ADDITIONAL RESOURCES
  53. 53. NEXT STEPS
  54. 54. © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademar ks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accu racy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
  1. Gostou de algum slide específico?

    Recortar slides é uma maneira fácil de colecionar informações para acessar mais tarde.

×