Build Your Own SQL Server Private Cloud

Ben DeBow
CEO
FORTIFIED DATA
Build Your Own
SQL Server Private Cloud

www.devconnections.com
BUILD YOUR OWN SQL SERVER PRIVATE CLOUD
 CEO Fortified Data
 Working with SQL Server for 20yrs
 Author, speaker, and consultant focusing
on Performance, Scalability, and Availability
 E-mail: bdebow@fortifieddb.com
 Twitter: @BBQSQL
 Web/Blog: http://www. fortifieddb.com
ABOUT ME

 We own, deploy, manage everything
 We own, deploy, manage everything but don’t own
data center (i.e. co-location)
 We own, maybe deploy, maybe manage some stuff,
and don’t own the space
 We own, but don’t do much of anything else
 Managed services (both of these)
 We don’t care where anything is nor do we want to
deal with it
 What management really wants
 Out of sight, out of mind, and few(er) FTEs
 Things just work, no issues (availability, performance,
reliability)
THE EVOLUTION OF IT

TYPICAL ARCHITECTURES YESTERDAY
Node 1
IN01
Node 2
IN02
Node 3
IN03
Node 4
WSFC
Hyper-V Hosts
Server1 Server2 ServerX
SQL ConsolidationServer
Sprawl

 OS and all related software run as a
guest under a host running a hypervisor
 Host can run many virtual machines
 Everything in the virtual machine is
(relatively) isolated
 != consolidation (but a technique of ..)
WHAT IS VIRTUALIZATION?
Hypervisor Host
Storage
Processing
VM
vNIC
vDisk
Host
Networking
vSwitch

 Potentially better use of hardware
 Potentially better isolation for specific
workloads
 Reduces physical footprint
 Saves money in tangible costs
 Easy to migrate and move
 Data center migrations
 New hardware
 Time to deploy reduced
 Elasticity
WHY VIRTUALIZE?

PHYSICAL VS. VIRTUAL DEPLOYMENTS
 It doesn’t need to be a standoff
 Both have their place
 Key factors: the –abilites
 May have some differences (e.g. how you
can/should do high availability)
 Virtualization is usually IT driven
 Reality: just like having a physical from an admin
standpoint
 Critical applications
 Sometime they just want physical

VIRTUALIZATION AND SQL SERVER
 Most of the same rules for physical
deployments apply for configuring SQL
Server in a virtualized environment
 Need to understand capacity
 vCPU = 1 core or a % of a core
 Depends on the configurations
 Can overcommit to a point
 Watch overcommitting
 Memory
 CPU

DEMO
9

THE CLOUD …

 It’s Magic!
 Your stuff is out there for you
 Access anywhere, anytime
 Do not have to worry about
 Availability
 Backups
 Administration
 Upgrades
 Consumer traction
 Dropbox, Office 365, iTunes, etc.
THE PROMISE OF THE CLOUD

Making Things Less Cloudy
PaaSHybrid IT
Most Control Least Control
DedicatedShared
Physical Servers Virtual Machines Hosted VMs Hosted DBs
IaaS
IaaS

 Lower/control costs
 Reality: maybe
 We manage everything – no worries!
 Reality: are you sure? Is that what you want
(including patching)?
 Scales to what you need
 Reality: maybe
 Good availability and reliability
 Reality: see recent Outlook.com and Amazon
EC2 outages
 Security
 Reality: maybe
PUBLIC CLOUD MESSAGES VS. REALITY

 Private cloud/Hybrid IT for SQL Server
 Think of yourself or group as a service provider to
your customers, even if “just” internal
 Managed services
 Provide standardized, end-to-end offerings
 Varying levels of guaranteed service (uptime,
performance)
 Predictable costs, outcomes
 Account for exceptions
 Some things cannot fit into standard offerings
 Charge accordingly
SQL SERVER AS A SERVICE (SQLAAS)

DEMO
15

 Automation of most, if not all, tasks
 Self-service should be the end goal
 Define and implement the right processes
 Communication important; processes may involve other
teams
 Define clear tiers and services that go with them
 HW or VM profile
 Availability
 Scalability
 Good monitoring at all levels
 Thin vs. thick provisioning
 Chargeback?
KEYS TO PRIVATE CLOUD SUCCESS

SYSTEM CENTER 2012 AND SQL SERVER
From http://tinyurl.com/p28ql7f)

 Space not mature just yet
 Think virtualization 5 or 6 years ago
 Will not replace on premise or private cloud yet
 Application databases that are a fit
 Windows Azure Database
 Will not be affected by possible limitations
 Costs controlled
 Full deployment (EC2, Windows Azure IaaS)
 Understand admin (incl. backups), etc.
 Disaster recovery
 Most common desire we see
 Can app flip to the cloud?
USING THE PUBLIC CLOUD

 Different ways to control costs and
increase utilization and agility
 Virtualization is here to stay
 The cloud may not be what you thought it
was
 Promise vs. the reality of the cloud
 Adapt to the cloud – will be part of your
DBA world sooner rather than later
SUMMARY

QUESTIONS
20

REFERENCES
• Microsoft Private Cloud
• http://www.microsoft.com/en-us/server-cloud/private-cloud/default.aspx
• VMware Private Cloud
• http://www.vmware.com/solutions/business-critical-apps/sql-virtualization/sql-private-
cloud.html
• Fast Track Partners
• http://www.microsoft.com/en-us/server-cloud/private-cloud/hyperv-cloud-fast-
track.aspx
• SQL Server 2012 Cloud
• http://www.microsoft.com/sqlserver/en/us/future-editions/SQL-Server-2012-cloud-
on-your-terms.aspx
• SQLCAT – SQL Server Private Cloud
• http://sqlcat.com/sqlcat/b/whitepapers/archive/2011/03/22/onboarding-sql-
server-private-cloud-environment.aspx

Build Your Own SQL Server Private Cloud

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Empfohlen

Empfohlen (20)

Build Your Own SQL Server Private Cloud