Extending your data to the cloud

Editor's Notes

• #7: Comparison between SQL Azure and SQL ServerHighlight the differences between SQL Server and SQL Azure (emphasize the PaaS aspect since SQL Azure is fully managed as opposed to a VM in the cloud)Emphasize the differences between “Server” and “Service” and the flexibility that comes with it (pay as you go, fully managed) etcEnd by Highlighting the common tools and programming model across both SQL Server and SQL Azure Same T-SQL based programming model, tools like Visual Studio, SSMS, SSMA, SSIS bcpetcAlso highlight about tools to migrate data to SQL Azure
• #8: Recap Earlier Discussion by reminding audience of three key principles which distinguish SQL AzureUse this section to first remind audience that we are extending the same SQL Server based information platform to the cloudExplain that we have features like Database, Data Sync and Reporting to highlight the fact that it is more than just database in the cloudRe-iterate pillars and talk about features like self-managing, multiple copies of data, built in HA and fault tolerance etc
• #9: Slide ObjectiveUse this slide to transition into an explanation of SQL Azure Database (Reporting and Data Sync will be covered later)Explain at a high level how SQL Azure worksSpeaker NotesDesign Principle of SQL Azure: Focus on combining the best features of SQL Server running at scale with low frictionSQL Azure is a high availability databaseAlways three transaction consistent replicas of the databaseOne primary replica; two slave replicasFailure of a replica will result in another replica being spun up immediately by the fabricFailure of the primary replica means a slave replica will become the primary and a new slave will spin upMinimal down timeTypically just a few dropped connectionsEasy to code for the failover scenario- if you are ding god connection management and error handling will be fineClustered index required on all tables to allow replicationNotesUseful article from SQL Azure teamhttp://msdn.microsoft.com/en-us/magazine/ee321567.aspx
• #10: Security
• #11: Slide ObjectiveDiscusses various SQL Azure data access topologiesSpeaking notesAccess from within Microsoft Datacenter (Code near scenario)Connect a Windows Azure Compute application to SQL AzureExecuting Asp.NET code, PHP, other managed code, native codeSimple familiar programming modelAccess from on premise applications (Code far)Solve the DB under the desk issue.NET, native or other platform supportMicrosoft access as a front end offers interesting scenarioNeed to be conscious of query frequency and/or payloadAccess from both Cloud and On PremiseE.g. application with browser front and AND a need to sync to mobile devicesCloud provides an always up rendezvous point for data consumersWindows Azure runs the browser based applicationOther applications connect remotely- TDS, Odata, SncNotesMSDN on topology optionshttp://msdn.microsoft.com/en-us/library/ee336239.aspxSQL Azure + MS Accesshttp://blogs.msdn.com/b/access/archive/2010/06/07/access-2010-and-sql-azure.aspx
• #12: Elastic ScaleService scales as resources requirements growNo-Code Sync ConfigurationEasily define data to be synchronizedSchedule SyncChoose how often data is synchronizedConflict HandlingHandle issues where same data is changed in multiple locationsLogging and MonitoringAdministration capabilities for tracking data and monitoring potential issues
• #19: Best TCODesigned for Internet ScaleSQL Azure is fully managed database as a service built on an elastic scale-out infrastructure optimized for Internet scale workloads such as SaaS ISV and Web Business applications.Amazon RDS is a partially managed, traditional VM hosted scale-up modelHigh Availability Built InSQL Azure: all DBs have 3 replicas with automatic recovery from network, hardware, and software failures baked inAmazon RDS: you have pay extra (2X) for less (traditional 2 node failover)Transparent MaintenanceSQL Azure: we perform rolling platform updates (hardware upgrades, software patching, etc.) transparently with no application downtimeAmazon RDS: your database is regularly taken offline for software patchingUnique InnovationBusiness IntelligenceSQL Azure works today with Microsoft’s familiar BI tools (Office, SSRS, SSAS); innovative roadmap of cloud BI services coming in next 12 months (reporting service CTP coming late CY10; analytics in CY11)Data marketplace (Dallas) enables aggregation and rich visualization of both public and private information sourcesAmazon RDS offers no BI capabilitiesPower of the Cloud In Your DatacenterWindows Azure Platform Appliance: On-premises appliance offers same functionality and services as SQL AzureAppFabric Service Bus and SQL Azure Data Sync: extend your existing applications and databases to the cloud securely and in real-timeFamiliar and ProductiveLess Complex; Better ValueSQL Azure has simpler billing – everything is bundled, consistent and easy to comprehend. It also provides more at lower price, high-availability is an inherent feature of the service vs. Amazon RDS, which requires additional paid nodesAmazon RDS prices individual meters – storage, bandwidth charged separatelyDeveloper Platform and Broad EcosystemSQL Azure: Leverage familiar T-SQL and .NET based application model (Transact-SQL, ADO.NET, OLE DB, ODBC, and JDBC, LINQ, Entity Framework, WCF Data Services)Integration with existing tools to ensure rapid development and reuse of existing skillset and best practices (Visual Studio, SQL Server Management Studio , Migration tools for SQL Server, Access and MySQL)
• #21: Elastic ScaleService scales as resources requirements growNo-Code Sync ConfigurationEasily define data to be synchronizedSchedule SyncChoose how often data is synchronizedConflict HandlingHandle issues where same data is changed in multiple locationsLogging and MonitoringAdministration capabilities for tracking data and monitoring potential issues