En esta presentación examinamos los roles y responsabilidades en la administración de SQL Azure. Saludos, Eduardo Castro Martinez – Microsoft SQL Server MVP http://mswindowscr.org http://comunidadwindows.org Costa Rica Technorati Tags: SQL Server LiveJournal Tags: SQL Server del.icio.us Tags: SQL Server http://ecastrom.blogspot.com http://ecastrom.wordpress.com http://ecastrom.spaces.live.com http://universosql.blogspot.com http://todosobresql.blogspot.com http://todosobresqlserver.wordpress.com http://mswindowscr.org/blogs/sql/default.aspx http://citicr.org/blogs/noticias/default.aspx

1. Roles and Responsibilities Managing a Microsoft SQL Azure Ing. Eduardo Castro, PhD GrupoAsesor en Informática ecastro@grupoasesor.net

2. Agenda Introduction to SQL Data Services (SDS) SDS Concepts Demo: Provisioning of SDS Server and Database Managing SDS Database

3. The New SQL Data Services Database as a service Focus on combining the best features of SQL Server running at scale with ease of use High compatibility with existing SQL Server offering In V1, addresses web/departmental workloads

4. Data Platform: Device to Cloud RDBMS Service Mining Protection Sync Load Reporting Caching Query Analysis Integration Search Backup Model & policy based development and management In Memory RelationalBLOB MultiDim XML File Type Place Mega-server Desktop Data Services Server Mobile/Desktop

5. Database Choices Value Props: Full h/w control – size/scale 100% of API surface area Roll-your-own HA/DR/scale Value Props: 100% of API surface area Roll-your-own HA/DR/scale Dedicated On-premise SQL Server or other s/w on-premise Resource governance @ machine Security @ DB Server/OS Value Props: Auto HA, Fault-Tolerance Friction-free scale Self-provisioning Subset of API surface area Resources Hosted Hosted SQL Server Resource governance @ VM Security @ DB Server/OS SDS Virtual DB server Resource governance @ DB Security @ DB/Virtual Server Shared Low “Friction”/Control High SDS V1 targets scenarios that live in the lower left quadrant

6. SDS Concepts Provisioning model Account, server, database Traditional SQL security model Authenticate logins, map to users and roles Authorize users and roles to SQL objects Familiar SQL programming model Traditional SQL Server relational model Support ADO.Net, ODBC Applications must be partition aware for larger databases

7. Azure™ Services Platform Azure Services Platform

8. The Microsoft Platform Stack Mobile Desktop Server Cloud Application Data OS

10. Future Offerings

11. Additional data platform capabilities as a service: BI/DSS, DW

12. New services: Reference Data, Secure Data Hub

14. SDS Server and Database Provisioning demo

15. Architecture Shared SQL infrastructure Each user database is replicated to multiple servers Client requests are routed to current “primary database” State-of-the-art HA technology Automatic failure detection; client request re-routed to new primary Load balancing across shared resource pool Gateway provides TDS entry point, provisioning capability Machine 2 Machine 3 Machine 4 Machine 1 SQL Instance SQL Instance SQL Instance SQL Instance SQL DB SQL DB SQL DB SQL DB UserDB1 UserDB3 UserDB4 UserDB2 UserDB1 UserDB2 UserDB3 UserDB4 UserDB5 UserDB2 UserDB3 UserDB4 UserDB1 UserDB5 UserDB3 UserDB4 TDS entry point, provisioning High Availability Fabric: Failover and Load balancing

16. High Level Architecture SQL Data Services Gateway Tier Protocol Parser Protocol Parser Protocol Parser Protocol Parser Protocol Parser Protocol Parser Protocol Parser Management Services Management Services Management Services Management Services Management Services Management Services Management Services Partition Services Partition Services Partition Services Partition Services Partition Services Partition Services Partition Services SQL Data Services Back End SQL Server SQL Server SQL Server SQL Server SQL Server SQL Server SQL Server Distributed Data Fabric Distributed Data Fabric Distributed Data Fabric Distributed Data Fabric Distributed Data Fabric Distributed Data Fabric Distributed Data Fabric Mgmt. Services Mgmt. Services Mgmt. Services Mgmt. Services Mgmt. Services Mgmt. Services Mgmt. Services

17. Data Hub “An aggregation of Enterprise, Partner, Desktop, and Device data within SQL Data Services” Windows Azure Enterprise Azure App On-premises App ADO.NET, ODBC, PHP, ... SQL Data Services Data Sync Service Sync Enterprise Sync Sync User Management Device Device Management Desktop Client App Client App Sync Gateway Business Logic / Rules Sync Client Sync Client

18. Data Hub – Project “Huron” Customer Segment Small and medium sized businesses Enterprise – rapid prototype Both Microsoft (v1) and Non-Microsoft device (post v1) Common Patterns Mobile device access to corporate data Business to business sharing Secure digital data hub / partner extranets Governmental data (searchable encryption)

19. Data Sync Service Analytical Sync Framework TDS Reporting SDS Provider SQL Data Services Data Sync Online Publish API Subscribe API Sync API 3rd party platforms Client Library API Client Library API Windows Desktops & Devices Sync Framework Sync Framework Sync Service Proxy Sync Service Proxy 3rd party DB Client Data Provider Client Data Provider

20. SQL Data Services Network Topology Applications use standard SQL client libraries: ODBC, OLEDB, ADO.Net, … Application TDS (tcp:1433) Load balancer forwards ‘sticky’ sessions to TDS protocol tier Load Balancer TDS (tcp: 1433) Gateway Gateway Gateway Gateway Gateway Gateway Data Node Data Node Data Node Data Node Data Node Data Node TDS (tcp: 1433) Scalability and Availability: Fabric, Failover, Replication and Load balancing

21. Scaling Out With SQL Data Services How 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

22. An Example Scale Out Architecture ASP.Net Application Customer 123 Partition Aware App Tier Data Partitions “Shards”

23. Software Installation and Patching SDS Responsibilities Software installation, patching and upgrade Minimum interruption to service DBA Responsibilities Install, upgrade your own schema Support application and multi-server management model

24. Monitoring and Problem Resolution SDS Responsibilities Service health is continuously monitored Hardware, availability, resource usage and etc Self-healing Automatic failover Load-balancing Dedicated MS operation team 24/7 Service dashboard for up-to-date health status DBA Responsibilities Relax and just use the service

25. High Availability and Disaster Recovery SDS Responsibilities Provide automatic local HA capability Post V1, provide DR capability Database is automatically backed up with easy recovery for system errors DBA Responsibilities Export of data to protect against user errors “Clone” a database Post V1, make available “self-service” restore

26. Database Admin Compatibility Goals Support common application patterns and TSQL functionality Support common DBA tasks Focus on logical data administration Physical administration provided by service

27. Logical Administration Database Schema Design Database User and Permission Management Index Management Query Tuning Statistics Management Data Import/Export Reporting … DBA knowledge is compatible with on-premise SQL

28. Logical vs. Physical Administration Supported Create/Drop database Create/Drop table Create/Drop user Index rebuild Update statistics … Not Supported Database file placement Filegroup management Server configuration options Mirroring …

29. Example: CREATE TABLE CREATE TABLE [[[ database_name . ] schema_name . table_name ( { <column_definition> | <computed_column_definition> | <column_set_definition> } [ < table_constraint> ] [ ,...n ] ) [ ON { partition_scheme_name … | filegroup | "default" } ] [ TEXTIMAGE_ON … ] [WITH ( < table_option > [ ,...n ] ) ] … No support for placement ex: FILEGROUP, TEXTIMAGE

30. Performance Troubleshooting Detect blocking query and deadlocks Query optimization Top N expensive queries Excessive recompile, bad query plan Index tuning Some of existing SQL facilities will continue to work SET SHOWPLAN SET STATISTICS DMV/DMF like system views …

31. Management Tooling Tools that will work SQL Server Management Studio SSIS and BCP SSRS Tools that will not work in the current form SQL profiler SQL performance counter …

32. http://www.grupoasesor.nethttp://comunidadwindows.orghttp://ecastrom.blogspot.comhttp://blogs.msdn.com/ssds/ http://www.microsoft.com/windowsazure/sqlazure/ http://sqlazuremw.codeplex.com/ Ing. Eduardo Castro, PhD GrupoAsesor en Informática ecastro@grupoasesor.net

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.