Session delivered to SQL Relay 2015 in Nottingham. In this session we look at some of the fundamental elements that you need to understand in order to build an IaaS solution that will meet the requirements to be covered by the Microsoft availability SLA. Additionally we will look at building a Microsoft Azure IaaS Solution. Demo Code available at: http://1drv.ms/1PC8707 *Note if you want to use the demo code you will need a Microsoft Azure subscription.

1. MICROSOFT AZURE
Building your first IaaS Configuration

2. Tuning blog: http://www.sqlperformance.com/
E-mail ebooks@sqlsentry.com for free copies of our $10 e-books:

3. DEMO CODE
• Demo code for this presentation can be found at;
http://1drv.ms/1PC8707

4. YOUR PRESENTER
• John Q Martin
o Sales Engineer for SQL Sentry
o Worked with SQL Server for ~10 years
o Consultant, SQL DBA, Dev & BI Developer
o Former Microsoft Premier Field Engineer
• Contact Information
o Email: Jmartin@SQLSentry.com
o Twitter: @SQLServerMonkey
o LinkedIn: https://uk.linkedin.com/in/johnqmartin

5. AGENDA
• Azure Fundamentals
• Important Design Considerations
o Availability
• Building a Simple Infrastructure in IaaS
• Summary
• Wrap Up

6. WHAT IS CLOUD?
• Cloud is doing your processing
somewhere else with someone else’s
systems.
• We have been doing it for years!
o It has had many names and taken many forms.

7. WHAT IS AZURE?
• Azure is a collection of services provided by Microsoft in their
Data Centres located around the globe.

8. WHAT IS AZURE?
• Azure is a collection of services provided by Microsoft in their
Data Centres located around the globe.
• You can control where your data resides in the Azure cloud by
selecting the geographic location.
o You can replicate data between geo-political regions but by default Microsoft does not.
• SLAs are by service & relate to availability, not performance.
o Will differ between services and have specific requirements.

9. WHAT IS AZURE?
• You pay for what you use
o Identify the frequency and costs associated with the different services.
o You can scale up/out and back down again as your needs require.
• Very easy to build and tear down environments.
o Turn off services when you are not using them to minimise costs.

10. AZURE DESIGN CONCEPTS
• Important to understand what the requirements are to qualify for
the SLAs
• SLA for VMs is 99.95%
o Multiple VMs serving the same service with fault tolerance designed in.

11. AZURE VM SLA
"Maximum Available Minutes" is the total accumulated
minutes during a billing month for all Internet facing Virtual
Machines that have two or more instances deployed in the
same Availability Set. Maximum Available Minutes is
measured from when at least two Virtual Machines in the
same Availability Set have both been started resultant from
action initiated by you to the time you have initiated an
action that would result in stopping or deleting the Virtual
Machines.

12. AZURE AVAILABILITY SETS
• An Availability set is a configuration of virtual machines that have
been deployed over different fault domains.
• A fault domain is a collection of servers that share common
resources
o Think of this as a rack of equipment.

13. AZURE AVAILABILITY SETS

14. AZURE FAULT DOMAINS

15. DESIGN CONSIDERATIONS
• Group the service tiers
• Isolate storage by server
o Can use more than one storage
account if needed.
• Make use of Availability
Sets and Fault domains.
• Decouple and
compartmentalise
different tiers. Storage Account - 01 Storage Account - 02
Data Tier Cloud Service
Data Tier
Availability Set
vmSQL01 – VHD [OS]
vmSQL01 – VHD [Data..]
vmSQL01
vmSQL02 – VHD [OS]
vmSQL02 – VHD [Data..]
vmSQL02

16. DEMO
Lets build Something!

17. QUESTIONS

18. THANK YOU!
• Slides will be available at http://blogs.sqlsentry.com
• More information at:
o SQLSkills, et al
• E-mail ebooks@sqlsentry.com for free copies of our e-books:
o Just tell them where you met me
• My contact info for other questions:
o Email: Jmartin@SQLSentry.com
o Twitter: @SQLServerMonkey