1. Migrating to and Integrating with SQL Azure
Jeff Mlakar
Database Architect
Ernst & Young

2. About me
Computer Science and Mechanical Engineering degrees from the Engineering College at the University of Michigan
(pause for ‘boo’s)
Started in SQL Server 2000, C++, Started in .NET 1.1, BizTalk 2002
Currently work as a Database Architect at the accounting firm of Ernst & Young.
(Title has been referred to as Database Architect, SQL Lead Designer/Data Modeler, Senior Application Engineer, … so you tell me)
Work on applications to Steward/Manage/ReportOn data across global firm
Blog: ,

3. Discuss the why and how of Integrating with Cloud Databases
PURPOSE
Discuss the why and how of Integrating with Cloud Databases

4. Agenda What is the SQL Azure? Why Integrate On-Premises with Cloud?
Why have different data in Cloud? Why have same?
Key Challenges
Best Practices
What Microsoft is doing to alleviate the burden
DEMOS:
Migrate
Backup
Sync
You’re actually getting 2 for the price of 1 in this talk.

5. What is SQL Azure?
Microsoft’s cloud offering for a Relational Database Platform as a Service.

6. Cloud Services “IaaS” “PaaS” “SaaS” Host Build Consume Amazon
Software-as-a-Service
Consume
GMail
“SaaS”
Platform-as-a-Service
Build
Microsoft
“PaaS”
Infrastructure-as-a-Service
Host
Amazon
“IaaS”
Slide Objectives:
Explain the three established terms in the industry for cloud services
Speaking Points:
With this in mind, it’s important to understand how to talk about our Cloud Services offerings.
There is a lot of confusion in the industry when it comes to the cloud.
It’s important that you understand both what is happening in the industry and how we think about the cloud.
This is the most commonly used taxonomy for differentiating between types of cloud services.
The industry has defined three categories of services:
IaaS – a set of infrastructure level capabilities such as an operating system, network connectivity, etc. that are delivered as pay for use services and can be used to host applications.
PaaS – higher level sets of functionality that are delivered as consumable services for developers who are building applications. PaaS is about abstracting developers from the underlying infrastructure to enable applications to quickly be composed.
SaaS – applications that are delivered using a service delivery model where organizations can simply consume and use the application. Typically an organization would pay for the use of the application or the application could be monetized through ad revenue.
It is important to note that these 3 types of services may exist independently of one another or combined with one another.
SaaS offerings needn’t be developed upon PaaS offerings although solutions built on PaaS offerings are often delivered as SaaS.
PaaS offerings also needn’t expose IaaS and there’s more to PaaS than just running platforms on IaaS.

7. Cloud Services In-House Software Infrastructure Platform Software
Storage
Servers
Networking
O/S
Middleware
Virtualization
Data
Applications
Runtime
You manage
Infrastructure
(as a Service)
Storage
Servers
Networking
O/S
Middleware
Virtualization
Data
Applications
Runtime
Managed by vendor
You manage
Platform
(as a Service)
Managed by vendor
You manage
Storage
Servers
Networking
O/S
Middleware
Virtualization
Applications
Runtime
Data
Software
(as a Service)
Managed by vendor
Storage
Servers
Networking
O/S
Middleware
Virtualization
Applications
Runtime
Data
Slide Objectives:
Explain the differences and relationship between IaaS, PaaS, and SaaS in more detail.
Speaking Points:
Here’s another way to look at the cloud services taxonomy and how this taxonomy maps to the components in an IT infrastructure.
Packaged Software
With packaged software a customer would be responsible for managing the entire stack – ranging from the network connectivity to the applications.
IaaS
With Infrastructure as a Service, the lower levels of the stack are managed by a vendor. Some of these components can be provided by traditional hosters – in fact most of them have moved to having a virtualized offering.
Very few actually provide an OS
The customer is still responsible for managing the OS through the Applications.
For the developer, an obvious benefit with IaaS is that it frees the developer from many concerns when provisioning physical or virtual machines.
This was one of the earliest and primary use cases for Amazon Web Services Elastic Cloud Compute (EC2).
Developers were able to readily provision virtual machines (AMIs) on EC2, develop and test solutions and, often, run the results ‘in production’.
The only requirement was a credit card to pay for the services.
PaaS
With Platform as a Service, everything from the network connectivity through the runtime is provided and managed by the platform vendor.
The Windows Azure Platform best fits in this category today.
In fact because we don’t provide access to the underlying virtualization or operating system today, we’re often referred to as not providing IaaS.
PaaS offerings further reduce the developer burden by additionally supporting the platform runtime and related application services.
With PaaS, the developer can, almost immediately, begin creating the business logic for an application.
Potentially, the increases in productivity are considerable and, because the hardware and operational aspects of the cloud platform are also managed by the cloud platform provider, applications can quickly be taken from an idea to reality very quickly.
SaaS
Finally, with SaaS, a vendor provides the application and abstracts you from all of the underlying components.

8. SQL Azure Database The first and only true database as a service
Subtitle color
Managed Service
Scale On Demand
Innovate Faster
Easy provisioning and deployment
Auto high-availability and fault tolerance
No need for server or VM administration
Database utility; pay as you grow
Business-ready SLAs
Enable multi-tenant solutions
World-wide presence
Build cloud-based database solutions on consistent relational model
Leverage existing skills through existing ecosystem of developer and management tools

9. SQL Azure Physical Architecture
Apps
Tools
ODBC
ADO.NET
TDS
SQL Azure Services
Connection Routing
Billing
Provisioning
Server
Server
Server
SQL Server
SQL Server
SQL Server
SQL Azure Fabric
SQL Azure Fabric
SQL Azure Fabric
Infrastructure
Database 1
Database 2
Database 3

10. SQL Azure Logical Architecture

11. SQL Azure High Availability offering!
Single Database
Multiple Replicas
Replica 1
Single Primary
Replica 2 DB
Replica 3
Replica 4

12. Physical vs. Logical Administration
Service handles physical administration
Automatically provides HA “out of box”
Transparent failover in case of failure
Load balancing of data to ensure SLA
You focus on logical administration
Schema creation and management
Query optimization
Security management (Logins, Users, Roles)

13. So what does this COST?

14. So what does this COST? (cont)
Source:

15. Why Integrate?

16. Why do Companies want to Integrate On-Premises With Cloud?
Regulatory
HIPAA
PCI
Fear, uncertainty, doubt
Functionality
Some companies syncing Cloud to Prem to perform full text data search
Some on prem solutions may require CLR procedures, extended properties, etc.

17. Same data in Cloud vs. Different data
Why have Same?
Good failover option
SQL Azure Data sync makes the process easy
Open Source tools like SQL Azure Migration Wizard make deployment easy
Why have Different?
HIPAA, PCI restrictions
Different data types/functional Requirements needed on Prem
May use Cloud as backup since inbound data is free

18. Key Challenges Refactoring required for
Service Broker solutions
Replication solutions
Cross Database calls
Unsupported data types
Extended Properties
Tables requiring Clustered Indexes
Silverlight Management Tool very slow for large number of objects
Size limitations (150 GB)

19. Best Practices Deployment / Migration: Integration:
SQL Azure Migration Wizard (
Redgate SQL Compare Tools
Data Tier Application Framework
Integration:
SQL Azure Data Sync
Using Azure App Fabric to connect from Cloud Application to prem Database

20. What is Microsoft doing to help?
Constant updates
To Azure functionality/features
To Management portal
Data Sync Integrated
Data Tier Application Framework in SQL Server 2012
Bacpac files to Azure Storage Instance

21. demos
How To Migrate

22. How To Migrate Demos Script to Azure from SSMS
SQL Azure Migration Wizard
Redgate SQL Compare
Data Tier Application Framework
Extract/Deploy dacpac
Export bacpac to file
Show you can examine bacpac file
Export bacpac to Windows Azure
Import bacpac in Portal
Deploy to SQL Azure to new Server
Backup in SSMS
Restore to prem in SSMS

23. demo
How To Integrate

24. How To Integrate Demo
SQL Azure Data sync

25. Questions?