Data Migration and Data-Tier Applications with SQL Azure


Published on

SQL Saturday Philadelphia March 5, 2011, Migrating SQL Server database applications to SQL Azure with data migration and data-tier applications.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 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 team
  • So what are the requirements for this? It is part of Visual Studio 2010 functionality. Additionally, to deploy data-tier applications, you need to running SQL 2008 R2 (enterprise
  • This is a view of an expanded DACPAC—as you can see it consists of 3 SQL scripts—the main schema script and any pre and post deployment scripts. There are a couple of XML files that define the physical and logical models around the data. As vendors begin to use this technology as method to roll out databases for their technology, as DBAs this will be the place where we can preview their schema and identify any potential issues. Also, not that you would do this, but always review code in a dacpac you downloaded from an unknown source, to ensure that there isn’t any malicious code. In Visual Studio 2010 Premium and higher, you can compare two DACPAC schema files, or just use a file comparison tool.
  • Data Migration and Data-Tier Applications with SQL Azure

    1. 1. Migrate SQL Server Apps to SQL Azure Cloud DB<br />Mark Kromer, Microsoft<br />Joe D’Antoni, Synthes<br />
    2. 2. Session Objectives and Takeaways<br />Objectives:<br />Overview of SQL Azure Cloud DB<br />Migrate application databases to Azure<br />Demonstrate database migration from SQL Server to Cloud<br />Application Database Deployment with Data-Tier Application<br />
    3. 3. SQL Azure DatabaseThe first and only true relational database as a service<br />Subtitle color<br />Elastic Scale<br />Self-managed<br />Developer Agility<br /><ul><li>Build cloud-based database solutions on consistent relational model
    4. 4. Leverage existing skills through existing ecosystem of developer and management tools
    5. 5. Explore new data application patterns
    6. 6. Database utility; pay as you grow
    7. 7. Flexible load balancing
    8. 8. Business-ready SLAs
    9. 9. Enable multi-tenant solutions
    10. 10. World-wide presence
    11. 11. Easy provisioning and deployment
    12. 12. Auto high-availability and fault tolerance
    13. 13. Self-maintaining infrastructure; self-healing
    14. 14. No need for server or VM administration</li></li></ul><li>SQL Azure Database<br />Single Logical<br />Database<br />Multiple PhysicalReplicas<br />Replica 1<br />Single Primary<br />Based on SQL Server 2008 R2 engine<br />Use same tools and data access frameworks<br />Six global datacenters<br />High Availability & Redundancy<br />Reads are completed at the primary<br />Writes are replicated to a quorum of secondaries<br />Replica 2<br />DB<br />Replica 3<br />Multiple<br />Secondaries<br />
    15. 15. Application Topologies<br />SQL Azure Access from within and outside <br />MS Datacenter<br />(On-premises & Azure Compute)<br />SQL Azure Access from outside<br /> MS Datacenter<br />(On-premises)<br />SQL Azure access from<br />within MS Datacenter <br />(Azure compute)<br />SQL Server<br />App code/ Tools<br />App code/ Tools<br />Application/ Browser<br />SOAP/REST<br />HTTP/S<br />Astoria/REST - EDM<br />HTTP/S<br />Windows<br />Azure<br />SQL Azure<br /> Data Sync<br />App Code<br />(ASP.NET)<br />App Code<br />(ASP.NET)<br />T-SQL (TDS)<br />App Code<br />(ASP.NET)<br />App Code<br />(ASP.NET)<br />T-SQL (TDS)<br />T-SQL (TDS)<br />Windows<br />Azure<br />SQL Azure <br />SQL Azure <br />SQL Azure <br />Code Near<br />Code Far<br />Hybrid<br />
    16. 16. demo<br />SQL Azure Database Management<br />
    17. 17. demo<br />Application Migration from On-Premises SQL Server to SQL Azure in the Cloud<br />
    18. 18. demo<br />Database Migration from SQL Server to SQL Azure<br />
    19. 19. Introducing SQL Azure Data Sync”Synchronization of SQL Server and SQL Azure Databases”<br />CTP1 (Now)<br />SQL Azure Database<br />Sync<br />Sync<br />SQL Azure <br />Data Sync<br />Remote Offices<br />Retail Stores<br />Sync<br />Sync<br />Sync<br />Sync<br />Sync<br />CTP2<br />On-Premises (Headquarters)<br />
    20. 20. On-Premises to Cloud Symmetry<br /> SQL Server to SQL Azure Sync<br />SQL Azure<br />Benefits<br /><ul><li>Makes cloud extension rather than replacement
    21. 21. Enables moving workload to cloud in stages preserving investment in existing infrastructure
    22. 22. New scenarios spanning enterprise, cloud</li></ul>Sync<br />
    23. 23. SQL Azure to SQL Azure Synchronization<br />Benefits<br /><ul><li>Geo-synchronization of data across data centers
    24. 24. Scale-out read or read/write</li></li></ul><li>Extending Data to Retail and Remote Offices<br />SQL Azure to SQL Server Sync<br />Benefits<br /><ul><li>Share data with remote and retail offices, bringing data closer to the end-users
    25. 25. Lower latency – data access doesn’t require round trips
    26. 26. Higher availability – app still runs if server is unreachable
    27. 27. Reduced network utilization – most data access is local</li></ul>SQL Azure<br />
    28. 28. SQL Azure Data Sync CTP1<br />(Available now from <br /><br />Sync End to End Scenarios<br />Offline <br />Applications<br />Sync<br />Sync<br />Sync<br />Sync<br />On-Premises Applications<br />Sync<br />Sync<br />Sync<br />SQL Azure Database<br />Sync<br />Sync<br />Sync<br />Microsoft Sync Framework 4.0 <br />CTP available now! <br />Retail & Remote Offices<br />SQL Azure Data Sync<br /><br />SQL Azure Data Sync CTP2<br />(Coming in near future)<br />
    29. 29. Data Tier Applications<br />Data-Tier Application Project<br />(Departmental apps in V1)<br /><ul><li>New feature in SQL Server 2008 R2
    30. 30. Allows developers to own the database schema and definitions
    31. 31. Still needs work (more to come)
    32. 32. Microsoft seems to have invested deeply to build this, so it will get better (hopefully)
    33. 33. Interacts with SQL Azure—this is one method of deploying application code there</li></ul>Visual Studio<br />Build<br />Deploy<br />.dacpac<br />SQL Azure<br />
    34. 34. Software Requirements <br />
    35. 35. What’s in a DACPAC? <br />
    36. 36. demo<br />Application Deployment to SQL Azure using Data Tier Applications<br />
    37. 37. Thank you!<br />Mark Kromer, Microsoft<br />Joe D’Antoni, Synthes<br /><br /><br /><br />Philadelphia SQL Server User Group VP<br /><br /><br />