Data Migration and Data-Tier Applications with SQL Azure
•Download as PPTX, PDF•
2 likes•1,486 views
SQL Saturday Philadelphia March 5, 2011, Migrating SQL Server database applications to SQL Azure with data migration and data-tier applications.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Data Migration and Data-Tier Applications with SQL Azure
Similar to Data Migration and Data-Tier Applications with SQL Azure (20)
More from Mark Kromer
More from Mark Kromer (20)
Recently uploaded
Recently uploaded (20)
Data Migration and Data-Tier Applications with SQL Azure
- 1. Migrate SQL Server Apps to SQL Azure Cloud DB Mark Kromer, Microsoft Joe D’Antoni, Synthes
- 2. Session Objectives and Takeaways Objectives: Overview of SQL Azure Cloud DB Migrate application databases to Azure Demonstrate database migration from SQL Server to Cloud Application Database Deployment with Data-Tier Application
- 4. Leverage existing skills through existing ecosystem of developer and management tools
- 5. Explore new data application patterns
- 6. Database utility; pay as you grow
- 11. Easy provisioning and deployment
- 12. Auto high-availability and fault tolerance
- 15. Application Topologies SQL Azure Access from within and outside MS Datacenter (On-premises & Azure Compute) SQL Azure Access from outside MS Datacenter (On-premises) SQL Azure access from within MS Datacenter (Azure compute) SQL Server App code/ Tools App code/ Tools Application/ Browser SOAP/REST HTTP/S Astoria/REST - EDM HTTP/S Windows Azure SQL Azure Data Sync App Code (ASP.NET) App Code (ASP.NET) T-SQL (TDS) App Code (ASP.NET) App Code (ASP.NET) T-SQL (TDS) T-SQL (TDS) Windows Azure SQL Azure SQL Azure SQL Azure Code Near Code Far Hybrid
- 16. demo SQL Azure Database Management
- 17. demo Application Migration from On-Premises SQL Server to SQL Azure in the Cloud
- 18. demo Database Migration from SQL Server to SQL Azure
- 19. Introducing SQL Azure Data Sync”Synchronization of SQL Server and SQL Azure Databases” CTP1 (Now) SQL Azure Database Sync Sync SQL Azure Data Sync Remote Offices Retail Stores Sync Sync Sync Sync Sync CTP2 On-Premises (Headquarters)
- 21. Enables moving workload to cloud in stages preserving investment in existing infrastructure
- 22. New scenarios spanning enterprise, cloudSync
- 25. Lower latency – data access doesn’t require round trips
- 26. Higher availability – app still runs if server is unreachable
- 27. Reduced network utilization – most data access is localSQL Azure
- 28. SQL Azure Data Sync CTP1 (Available now from http://azure.com) Sync End to End Scenarios Offline Applications Sync Sync Sync Sync On-Premises Applications Sync Sync Sync SQL Azure Database Sync Sync Sync Microsoft Sync Framework 4.0 CTP available now! Retail & Remote Offices SQL Azure Data Sync http://azure.com SQL Azure Data Sync CTP2 (Coming in near future)
- 30. Allows developers to own the database schema and definitions
- 31. Still needs work (more to come)
- 32. Microsoft seems to have invested deeply to build this, so it will get better (hopefully)
- 33. Interacts with SQL Azure—this is one method of deploying application code thereVisual Studio Build Deploy .dacpac SQL Azure
- 35. What’s in a DACPAC?
- 36. demo Application Deployment to SQL Azure using Data Tier Applications
- 37. Thank you! Mark Kromer, Microsoft Joe D’Antoni, Synthes http://www.sqlmag.com/blogs/sql-server-bi.aspx http://mssqldude.wordpress.com http://twitter.com/mssqldude Philadelphia SQL Server User Group VP http://joedantoni.wordpress.com http://twitter.com/jdanton
Editor's Notes
- 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
- 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.