SQL Server Data Services
1 like929 views
This document discusses building applications with SQL Data Services and Windows Azure. It provides an agenda that introduces SQL Data Services architecture, describes SDS application architectures, and how to scale out with SQL Data Services. It also discusses the SQL Data Services network topology and performance considerations for accessing SDS from applications.
SQL Server Data Services
- 1. Building Applications with SQL Data Services and Windows Azure Ing. Eduardo Castro, PhDGrupo Asesor en Informáticaecastro@grupoasesor.net
- 2. Building Applications with SQL Data Services and Windows Azure Session AgendaIntroduction to SQL Data ServicesWhat is a Data Hub and What Problems Does it SolveSQL Data Services ArchitectureSDS Application ArchitecturesScaling out with SQL Data Services
- 3. Data Platform: Device to CloudRDBMSServiceMiningProtectionSyncLoadReportingCachingQueryAnalysisIntegrationSearchBackupModel & policy based development and managementInMemoryRelationalBLOBMultiDimXMLFileTypePlaceMega-serverDesktopData ServicesServerMobile/Desktop
- 4. Azure™ Services PlatformAzure Services Platform
- 5. The Microsoft Platform StackMobileDesktopServerCloudApplicationDataOS
- 6. Extending SQL Data Platform to CloudReference DataBusiness IntelligenceData SyncReportingSQL Data Services (SDS)Database-as-a-ServiceSymmetric Programming ModelData Hub AggregationInitial services – core RDBMS capabilities as a service (SDS), Data Sync and Data Hub
- 8. Additional data platform capabilities as a service: BI/DSS, DW
- 9. New services: Reference Data, Secure Data Hub
- 10. Enable new uses of data to deliver differentiated business valueCompatibility GoalsSupport common application patternsLogical based administrationPatterns work for SDS and SQLMulti-tenancy considerationsThrottling and load balancingLimits on DB size, duration of transaction, etcV1: Address the needs of 95% or more web and departmental application
- 11. Sample of SQL CompatibilityIn Scope for v1Tables, indexes and viewsStored ProceduresTriggersConstraintsTable variables, session temp tables (#t)…Out of Scope for v1Distributed TransactionsDistributed QueryCLRService BrokerSpatial Physical server or catalog DDL and views
- 12. Service Provisioning ModelEach account has zero or more serversAzure wide, provisioned in a common portalBilling instrumentEach server has one or more databasesContains metadata about the databasesUnit of authenticationUnit of Geo-locationEach database has standard SQL objectsUnit of consistencyContains users, tables, views, indices, etc… Account Server Database
- 13. AzureIng. Eduardo Castro, PhDArchitecthttp://ecastrom.blogspot.comdemo
- 14. Data Hub “An aggregation of Enterprise, Partner, Desktop, and Device data within SQL Data Services”Windows AzureEnterpriseAzure AppOn-premises AppADO.NET, ODBC, PHP, ...SQL DataServices Data Sync Service SyncEnterpriseSyncSyncUser ManagementDeviceDevice ManagementDesktopClient AppClient AppSync GatewayBusiness Logic / RulesSync ClientSync Client
- 15. Data Hub – Project “Huron”Customer SegmentSmall and medium sized businessesEnterprise – rapid prototype Both Microsoft (v1) and Non-Microsoft device (post v1)Common PatternsMobile device access to corporate dataBusiness to business sharingSecure digital data hub / partner extranets Governmental data (searchable encryption)
- 16. Data Hub – Project “Huron”Value PropsLower operational expense and capital expenditureSelf-healing Highly available Out-of-the-box support for SQL Server and SQL CompactExtensible to non-MS devices and data sources (post v1)
- 17. Data Sync ServiceAnalyticalSync FrameworkTDSReportingSDS ProviderSQL Data ServicesData SyncOnlinePublish APISubscribe APISync API3rd party platformsClient Library APIClient Library APIWindowsDesktops& DevicesSync FrameworkSync FrameworkSync Service ProxySync Service Proxy3rd party DBClient Data ProviderClient Data Provider
- 18. SQL Data Services Network TopologyApplications use standard SQL client libraries: ODBC, OLEDB, ADO.Net, …ApplicationTDS (tcp:1433)Load balancer forwards ‘sticky’ sessions to TDS protocol tierLoad BalancerTDS (tcp: 1433)GatewayGatewayGatewayGatewayGatewayGatewayData NodeData NodeData NodeData NodeData NodeData NodeTDS (tcp: 1433)Scalability and Availability: Fabric, Failover, Replication and Load balancing
- 19. Performance ConsiderationsThe distance your application travels to perform data access will affect performance
- 20. SDS Application ArchitecturesSDS access from within MS Datacenter (Azure compute – ADO.NET)SDS access from outside MS Datacenter (On-premises – ADO.NET)BrowserApp Code / ToolsAstoria/REST - EFHTTP/SSOAP/RESTHTTP/SApp Code(ASP.NET)Windows AzureT-SQL (TDS)T-SQL (TDS)SQL Data ServicesSQL Data ServicesMSDatacenterMSDatacenterTopology supported for some apps
- 21. Code Far ApplicationsData is typically located outside the firewall from where your application runsDesign your application to handle latencyPre-fetch as much data as possible to provide a rich experience to your usersCache data locally
- 22. Code Near ArchitectureApplication Code runs within the same network that your data resides onWindows Azure provides a scalable hosting and compute platform for hosting your applicationsSQL Data Services and Windows Azure provide a “better together” experience
- 23. Scaling Out With SQL Data ServicesHow can I gain maximum performance from my data tier?What if my application has large data storage requirements?Scaling out with SQL Data Services addresses these requirements
- 24. An Example Scale Out ArchitectureASP.NetApplicationCustomer 123PartitionAwareApp TierDataPartitions“Shards”
- 25. Scaling out with SQL Data Servicesdemo Sync ServiceIng. Eduardo Castro, PhDArchitecthttp://ecastrom.blogspot.com
- 26. What Can I Do To Get Ready For SDS?Download SQL Server Express todayArchitect your applications for Scale OutConsider where your data access will liveWatch for CTP Announcement Coming Soon!!!
- 27. What Did We Learn?SDS data platform is real and in productionBuilt using SQL Server 2008 codebaseDelivery of rich relational database service – PDC ’09Relational database is key capability of the Azure platformSDS design and architecture supports a wide range of scenariosCloud Data Hub’s are a convenient place to consolidate and share data
- 28. Accessing SDS from ADO.Net Data Servicesdemo Sync ServiceIng. Eduardo Castro, PhDArchitecthttp://ecastrom.blogspot.com
- 29. High Level ArchitectureSQL Data Services Gateway TierProtocol ParserProtocol ParserProtocol ParserProtocol ParserProtocol ParserProtocol ParserProtocol ParserManagement ServicesManagement ServicesManagement ServicesManagement ServicesManagement ServicesManagement ServicesManagement ServicesPartition ServicesPartition ServicesPartition ServicesPartition ServicesPartition ServicesPartition ServicesPartition ServicesSQL Data Services Back EndSQL ServerSQL ServerSQL ServerSQL ServerSQL ServerSQL ServerSQL ServerDistributed Data FabricDistributed Data FabricDistributed Data FabricDistributed Data FabricDistributed Data FabricDistributed Data FabricDistributed Data FabricMgmt. ServicesMgmt. ServicesMgmt. ServicesMgmt. ServicesMgmt. ServicesMgmt. ServicesMgmt. Services
- 30. Addressing Latency With Windows AzureWindows Azure is co-located in the same datacenter as SQL Data ServicesWindows Azure providesPoint 3
- 32. Building Applications with SQL Data Services and Windows Azure Ing. Eduardo Castro, PhDGrupoAsesor en Informáticaecastro@grupoasesor.nethttp://comunidadwindows.nethttp://ecastrom.blogspot.com
- 33. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks 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 accuracy 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.