Roles y Responsabilidades en SQL Azure


Published on

En esta presentación examinamos los roles y responsabilidades en la administración de SQL Azure.

Eduardo Castro Martinez – Microsoft SQL Server MVP
Costa Rica
Technorati Tags: SQL Server
LiveJournal Tags: SQL Server Tags: SQL Server

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Roles y Responsabilidades en SQL Azure

  1. 1. Roles and Responsibilities Managing a Microsoft SQL Azure<br />Ing. Eduardo Castro, PhD<br />GrupoAsesor en Informática<br /><br />
  2. 2. Agenda<br />Introduction to SQL Data Services (SDS)<br />SDS Concepts<br />Demo: Provisioning of SDS Server and Database<br />Managing SDS Database<br />
  3. 3. The New SQL Data Services<br />Database as a service<br />Focus on combining the best features of SQL Server running at scale with ease of use<br />High compatibility with existing SQL Server offering<br />In V1, addresses web/departmental workloads<br />
  4. 4. 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 />
  5. 5. Database Choices<br />Value Props:<br />Full h/w control – size/scale<br />100% of API surface area<br />Roll-your-own HA/DR/scale<br />Value Props:<br />100% of API surface area<br />Roll-your-own HA/DR/scale<br />Dedicated<br />On-premise<br /> SQL Server or other s/w on-premise<br /> Resource governance @ machine<br /> Security @ DB Server/OS<br />Value Props:<br />Auto HA, Fault-Tolerance<br />Friction-free scale<br />Self-provisioning<br />Subset of API surface area<br />Resources<br />Hosted<br /> Hosted SQL Server<br /> Resource governance @ VM<br /> Security @ DB Server/OS<br />SDS<br /> Virtual DB server<br />Resource governance @ DB<br /> Security @ DB/Virtual Server<br />Shared<br />Low<br />“Friction”/Control<br />High<br />SDS V1 targets scenarios that live in the lower left quadrant<br />
  6. 6. SDS Concepts<br />Provisioning model<br />Account, server, database<br />Traditional SQL security model<br />Authenticate logins, map to users and roles<br />Authorize users and roles to SQL objects<br />Familiar SQL programming model<br />Traditional SQL Server relational model<br />Support ADO.Net, ODBC<br />Applications must be partition aware for larger databases<br />
  7. 7. Azure™ Services Platform<br />Azure Services Platform<br />
  8. 8. The Microsoft Platform Stack<br />Mobile<br />Desktop<br />Server<br />Cloud<br />Application<br />Data<br />OS<br />
  9. 9. 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
  10. 10. Future Offerings
  11. 11. Additional data platform capabilities as a service: BI/DSS, DW
  12. 12. New services: Reference Data, Secure Data Hub
  13. 13. Enable new uses of data to deliver differentiated business value</li></li></ul><li>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 />
  14. 14. SDS Server and Database Provisioning<br />demo<br />
  15. 15. Architecture<br />Shared SQL infrastructure<br />Each user database is replicated to multiple servers<br />Client requests are routed to current “primary database”<br />State-of-the-art HA technology<br />Automatic failure detection; client request re-routed to new primary<br />Load balancing across shared resource pool<br />Gateway provides TDS entry point, provisioning capability<br />Machine 2<br />Machine 3<br />Machine 4<br />Machine 1<br />SQL Instance<br />SQL Instance<br />SQL Instance<br />SQL Instance<br />SQL DB<br />SQL DB<br />SQL DB<br />SQL DB<br />UserDB1<br />UserDB3<br />UserDB4<br />UserDB2<br />UserDB1<br />UserDB2<br />UserDB3<br />UserDB4<br />UserDB5<br />UserDB2<br />UserDB3<br />UserDB4<br />UserDB1<br />UserDB5<br />UserDB3<br />UserDB4<br />TDS entry point, provisioning<br />High Availability Fabric: Failover and Load balancing<br />
  16. 16. 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 />
  17. 17. 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 />
  18. 18. 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 />
  19. 19. 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 />
  20. 20. 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 />
  21. 21. 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 />
  22. 22. 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 />
  23. 23. Software Installation and Patching<br />SDS Responsibilities<br />Software installation, patching and upgrade<br />Minimum interruption to service<br />DBA Responsibilities<br />Install, upgrade your own schema<br />Support application and multi-server management model<br />
  24. 24. Monitoring and Problem Resolution<br />SDS Responsibilities<br />Service health is continuously monitored<br />Hardware, availability, resource usage and etc<br />Self-healing<br />Automatic failover<br />Load-balancing<br />Dedicated MS operation team 24/7<br />Service dashboard for up-to-date health status<br />DBA Responsibilities<br />Relax and just use the service<br />
  25. 25. High Availability and Disaster Recovery<br />SDS Responsibilities<br />Provide automatic local HA capability<br />Post V1, provide DR capability<br />Database is automatically backed up with easy recovery for system errors<br />DBA Responsibilities<br />Export of data to protect against user errors<br />“Clone” a database<br />Post V1, make available “self-service” restore<br />
  26. 26. Database Admin Compatibility Goals<br />Support common application patterns and TSQL functionality<br />Support common DBA tasks<br />Focus on logical data administration<br />Physical administration provided by service<br />
  27. 27. Logical Administration<br />Database Schema Design<br />Database User and Permission Management<br />Index Management<br />Query Tuning<br />Statistics Management<br />Data Import/Export<br />Reporting<br />…<br />DBA knowledge is compatible with on-premise SQL<br />
  28. 28. Logical vs. Physical Administration<br />Supported<br />Create/Drop database<br />Create/Drop table<br />Create/Drop user<br />Index rebuild<br />Update statistics<br />…<br />Not Supported<br />Database file placement<br />Filegroup management<br />Server configuration options<br />Mirroring<br />…<br />
  29. 29. Example: CREATE TABLE<br />CREATE TABLE <br />[[[ database_name . ] schema_name . table_name<br /> ( { &lt;column_definition&gt; | <br /> &lt;computed_column_definition&gt; |<br /> &lt;column_set_definition&gt; }<br /> [ &lt; table_constraint&gt; ] [ ,...n ] ) <br />[ ON { partition_scheme_name … | filegroup | &quot;default&quot; } ] <br /> [ TEXTIMAGE_ON … ] <br />[WITH ( &lt; table_option &gt; [ ,...n ] ) ]<br />…<br />No support for placement ex: FILEGROUP, TEXTIMAGE<br />
  30. 30. Performance Troubleshooting<br />Detect blocking query and deadlocks<br />Query optimization<br />Top N expensive queries<br />Excessive recompile, bad query plan<br />Index tuning<br />Some of existing SQL facilities will continue to work<br />SET SHOWPLAN<br />SET STATISTICS <br />DMV/DMF like system views<br />…<br />
  31. 31. Management Tooling<br />Tools that will work<br />SQL Server Management Studio<br />SSIS and BCP<br />SSRS<br />Tools that will not work in the current form<br />SQL profiler<br />SQL performance counter<br />…<br />
  32. 32. http://www.grupoasesor.nethttp://comunidadwindows.orghttp://ecastrom.blogspot.com <br />Ing. Eduardo Castro, PhD<br />GrupoAsesor en Informática<br /><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 />