SQL Server Data Services

2,283 views

Published on

Web Cast sobre SQL Server Data Services.

Saludos,
Eduardo Castro – Microsoft SQL Server MVP
http://mswindowscr.org
http://comunidadwindows.org
Costa Rica

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

No Downloads
Views
Total views
2,283
On SlideShare
0
From Embeds
0
Number of Embeds
146
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

SQL Server Data Services

  1. 1. Building Applications with SQL Data Services and Windows Azure <br />Ing. Eduardo Castro, PhD<br />Grupo Asesor en Informática<br />ecastro@grupoasesor.net<br />
  2. 2. Building Applications with SQL Data Services and Windows Azure Session Agenda<br />Introduction to SQL Data Services<br />What is a Data Hub and What Problems Does it Solve<br />SQL Data Services Architecture<br />SDS Application Architectures<br />Scaling out with SQL Data Services<br />
  3. 3. Data Platform: Device to Cloud<br />RDBMS<br />Service<br />Mining<br />Protection<br />Sync<br />Load<br />Reporting<br />Caching<br />Query<br />Analysis<br />Integration<br />Search<br />Backup<br />Model & policy based development and management<br />In<br />Memory<br />RelationalBLOB<br />MultiDim<br />XML<br />File<br />Type<br />Place<br />Mega-server<br />Desktop<br />Data Services<br />Server<br />Mobile/Desktop<br />
  4. 4. Azure™ Services Platform<br />Azure Services Platform<br />
  5. 5. The Microsoft Platform Stack<br />Mobile<br />Desktop<br />Server<br />Cloud<br />Application<br />Data<br />OS<br />
  6. 6. Extending SQL Data Platform to Cloud<br />Reference Data<br />Business Intelligence<br />Data Sync<br />Reporting<br />SQL Data Services (SDS)<br />Database-as-a-Service<br />Symmetric Programming Model<br />Data Hub Aggregation<br /><ul><li>Initial services – core RDBMS capabilities as a service (SDS), Data Sync and Data Hub
  7. 7. Future Offerings
  8. 8. Additional data platform capabilities as a service: BI/DSS, DW
  9. 9. New services: Reference Data, Secure Data Hub
  10. 10. Enable new uses of data to deliver differentiated business value</li></li></ul><li>Compatibility Goals<br />Support common application patterns<br />Logical based administration<br />Patterns work for SDS and SQL<br />Multi-tenancy considerations<br />Throttling and load balancing<br />Limits on DB size, duration of transaction, etc<br />V1: Address the needs of 95% or more web and departmental application<br />
  11. 11. Sample of SQL Compatibility<br />In Scope for v1<br />Tables, indexes and views<br />Stored Procedures<br />Triggers<br />Constraints<br />Table variables, session temp tables (#t)<br />…<br />Out of Scope for v1<br />Distributed Transactions<br />Distributed Query<br />CLR<br />Service Broker<br />Spatial <br />Physical server or catalog DDL and views<br />
  12. 12. Service Provisioning Model<br />Each account has zero or more servers<br />Azure wide, provisioned in a common portal<br />Billing instrument<br />Each server has one or more databases<br />Contains metadata about the databases<br />Unit of authentication<br />Unit of Geo-location<br />Each database has standard SQL objects<br />Unit of consistency<br />Contains users, tables, views, indices, etc…<br /> Account<br /> Server<br /> Database<br />
  13. 13. Azure<br />Ing. Eduardo Castro, PhD<br />Architect<br />http://ecastrom.blogspot.com<br />demo <br />
  14. 14. Data Hub<br /> “An aggregation of Enterprise, Partner, Desktop, and Device data within SQL Data Services”<br />Windows Azure<br />Enterprise<br />Azure App<br />On-premises App<br />ADO.NET, ODBC, PHP, ...<br />SQL Data<br />Services<br /> Data Sync Service <br />Sync<br />Enterprise<br />Sync<br />Sync<br />User Management<br />Device<br />Device Management<br />Desktop<br />Client App<br />Client App<br />Sync Gateway<br />Business Logic / Rules<br />Sync Client<br />Sync Client<br />
  15. 15. Data Hub – Project “Huron”<br />Customer Segment<br />Small and medium sized businesses<br />Enterprise – rapid prototype <br />Both Microsoft (v1) and Non-Microsoft device (post v1)<br />Common Patterns<br />Mobile device access to corporate data<br />Business to business sharing<br />Secure digital data hub / partner extranets <br />Governmental data (searchable encryption)<br />
  16. 16. Data Hub – Project “Huron”<br />Value Props<br />Lower operational expense and capital expenditure<br />Self-healing <br />Highly available <br />Out-of-the-box support for SQL Server and SQL Compact<br />Extensible to non-MS devices and data sources (post v1)<br />
  17. 17. Data Sync Service<br />Analytical<br />Sync Framework<br />TDS<br />Reporting<br />SDS Provider<br />SQL Data Services<br />Data Sync<br />Online<br />Publish API<br />Subscribe API<br />Sync API<br />3rd party platforms<br />Client Library API<br />Client Library API<br />Windows<br />Desktops<br />& <br />Devices<br />Sync Framework<br />Sync Framework<br />Sync Service Proxy<br />Sync Service Proxy<br />3rd party DB<br />Client Data Provider<br />Client Data Provider<br />
  18. 18. SQL Data Services Network Topology<br />Applications use standard SQL client libraries: ODBC, OLEDB, ADO.Net, …<br />Application<br />TDS (tcp:1433)<br />Load balancer forwards ‘sticky’ sessions to TDS protocol tier<br />Load Balancer<br />TDS (tcp: 1433)<br />Gateway<br />Gateway<br />Gateway<br />Gateway<br />Gateway<br />Gateway<br />Data Node<br />Data Node<br />Data Node<br />Data Node<br />Data Node<br />Data Node<br />TDS (tcp: 1433)<br />Scalability and Availability: Fabric, Failover, Replication and Load balancing<br />
  19. 19. Performance Considerations<br />The distance your application travels to perform data access will affect performance<br />
  20. 20. SDS Application Architectures<br />SDS access from within MS Datacenter <br />(Azure compute – ADO.NET)<br />SDS access <br />from outside MS Datacenter <br />(On-premises – ADO.NET)<br />Browser<br />App Code / Tools<br />Astoria/REST - EF<br />HTTP/S<br />SOAP/REST<br />HTTP/S<br />App Code<br />(ASP.NET)<br />Windows Azure<br />T-SQL (TDS)<br />T-SQL (TDS)<br />SQL Data Services<br />SQL Data Services<br />MS<br />Datacenter<br />MS<br />Datacenter<br />Topology supported <br />for some apps<br />
  21. 21. Code Far Applications<br />Data is typically located outside the firewall from where your application runs<br />Design your application to handle latency<br />Pre-fetch as much data as possible to provide a rich experience to your users<br />Cache data locally<br />
  22. 22. Code Near Architecture<br />Application Code runs within the same network that your data resides on<br />Windows Azure provides a scalable hosting and compute platform for hosting your applications<br />SQL Data Services and Windows Azure provide a “better together” experience<br />
  23. 23. Scaling Out With SQL Data Services<br />How can I gain maximum performance from my data tier?<br />What if my application has large data storage requirements?<br />Scaling out with SQL Data Services addresses these requirements<br />
  24. 24. An Example Scale Out Architecture<br />ASP.Net<br />Application<br />Customer 123<br />Partition<br />Aware<br />App Tier<br />Data<br />Partitions<br />“Shards”<br />
  25. 25. Scaling out with SQL Data Services<br />demo <br />Sync Service<br />Ing. Eduardo Castro, PhD<br />Architect<br />http://ecastrom.blogspot.com<br />
  26. 26. What Can I Do To Get Ready For SDS?<br />Download SQL Server Express today<br />Architect your applications for Scale Out<br />Consider where your data access will live<br />Watch for CTP Announcement Coming Soon!!!<br />
  27. 27. What Did We Learn?<br />SDS data platform is real and in production<br />Built using SQL Server 2008 codebase<br />Delivery of rich relational database service – PDC ’09<br />Relational database is key capability of the Azure platform<br />SDS design and architecture supports a wide range of scenarios<br />Cloud Data Hub’s are a convenient place to consolidate and share data<br />
  28. 28. Accessing SDS from ADO.Net Data Services<br />demo <br />Sync Service<br />Ing. Eduardo Castro, PhD<br />Architect<br />http://ecastrom.blogspot.com<br />
  29. 29. High Level Architecture<br />SQL Data Services Gateway Tier<br />Protocol Parser<br />Protocol Parser<br />Protocol Parser<br />Protocol Parser<br />Protocol Parser<br />Protocol Parser<br />Protocol Parser<br />Management Services<br />Management Services<br />Management Services<br />Management Services<br />Management Services<br />Management Services<br />Management Services<br />Partition Services<br />Partition Services<br />Partition Services<br />Partition Services<br />Partition Services<br />Partition Services<br />Partition Services<br />SQL Data Services Back End<br />SQL Server<br />SQL Server<br />SQL Server<br />SQL Server<br />SQL Server<br />SQL Server<br />SQL Server<br />Distributed Data Fabric<br />Distributed Data Fabric<br />Distributed Data Fabric<br />Distributed Data Fabric<br />Distributed Data Fabric<br />Distributed Data Fabric<br />Distributed Data Fabric<br />Mgmt. Services<br />Mgmt. Services<br />Mgmt. Services<br />Mgmt. Services<br />Mgmt. Services<br />Mgmt. Services<br />Mgmt. Services<br />
  30. 30. Addressing Latency With Windows Azure<br />Windows Azure is co-located in the same datacenter as SQL Data Services<br />Windows Azure provides<br />Point 3<br />
  31. 31. question & answer<br />
  32. 32. Building Applications with SQL Data Services and Windows Azure <br />Ing. Eduardo Castro, PhD<br />GrupoAsesor en Informática<br />ecastro@grupoasesor.net<br />http://comunidadwindows.net<br />http://ecastrom.blogspot.com<br />
  33. 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.<br />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.<br />

×