Transcript > > > > > > Highly scaled out relational database as a service Browser SQL Azure Database (Windows Azure Compute) SOAP/REST HTTP/S • Highly scaled Database “as a Service” – beyond.

>
>
>
>
>
>
Highly scaled out relational database as a service
Browser
SQL Azure Database
(Windows Azure Compute)
SOAP/REST
HTTP/S
• Highly scaled
Database “as a Service” – beyond hosting
(ASP.NET)
Windows Azure
Compute
SQL Azure
Database
• SQL Server technology foundation
• Highly symmetrical
Astoria/REST - EDM
HTTP/S
App Code
T-SQL (TDS)
Relational database service
SQL Server Reporting
Server
(on-premises)
T-SQL (TDS)
MS
Datacenter
- AD Federation (LiveId /.Net Svcs ACS)
Customer Value Props
Self-provisioning and capacity on demand
Symmetry w/ on-premises database platform
Automatic high-availability and fault-tolerance
Automated DB maintenance (infrastructure)
Simple, flexible pricing – “pay as you grow”
Requirements
Analysis
Maintenance
Schema Design
Implementation
>
>
>
>
>
>
Newly added support in SSMS R2 is changing the game
demo
Development
• No uniform DB project system
and workflow
• No ability to capture deployment
intent
• Lack of T-SQL designers for
breadth developers
Management
Deployment
•
•
•
DBAs and Developers work
in silos
No clean app containment
once deployed
Time consuming and error
prone
•
•
•
Difficult to centrally control the
environment
SQL Server sprawl on the rise
Impact analysis & resource
planning is tricky, difficult
Development
• Data-tier Application project
• New T-SQL IDE in VS 2010
• Integrated editor, debugger,
IntelliSense, language service,
policy designer
• Static code analysis, build service
Long Term
Deployment
•
•
Easier to deploy and upgrade
Data-tier Apps from VS and
SSMS
Single unit of deployment has
app + developer intent
Management
•
•
•
Manage @ Scale: SQL Server
Control Point
Visualize resource utilization at
the instance & application level
Trending analysis helps improve
resource utilization, reduce costs
>
>
>
>
>
>
>
>
Schema
LOGICAL
Tables, Views,
Constraints, SProcs,
UDFs,
PHYSICAL
Users, Logins,
Indexes
>
DAC Deployment Profile
Deployment Requirements, Management
Policies, Failover Policies
>
>
>
Unit of Deployment
>
demo
Dev, Test, Prod
>
>
>
>
>
>
>
How can we do this better?
>
If an electronic device didn’t catch fire, it
was free to proceed for further testing
Smoke bombs were placed inside
chambers to ensure they were airtight
Where we are headed
Dev
Test
Prod
Having
Practices
built
in schema
makes
aupgrades
happy
Utilizing
aBest
DAC
handles
all packaged
the
When
ready,
changes
are
and
smoke
Our
developer
goes
about
their
day writing
new
Only
Higher
after
quality
smoke
gates
tests
prevent
pass
are
changes
changes
tosmoke
production
allowed
At the
same
time,
our
tester
is the
writing
tests
customer
automatically
tested
code
Tests are uploaded
and form an
enforcement SQL Azure
boundary Prod DB
DAC
SQL Azure
Dev DB
SQL Azure
Test DB
SQL Azure
UAT DB
>>FUTURE
>
>
>
>
>
>
>
>>FUTURE
“I want an easy way to just get in there
and start developing”
“My database is in the cloud, why can’t
my database development tools be?”
demo
>
>
>
>
>
>
>
>
>
>
channel9.msdn.com/learn
Built by Developers for Developers….
© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market
conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT
MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.