[MUSIC]
Hi, my name is Lindsey Allen, I'm one of the program managers at
Microsoft SQL Server engineering team.
In this video,
I'm going to talk about SQL Azure Database as a service.
So there's four different ways you can actually use
this great product for the SQL Server.
SQL Server is cloud-first but not cloud only.
You can take the SQL Server, install in your own data center.
The same SQL Server can be installed and running in Azure VM.
And the topic of this video is the same SQL Server
running as past service called Azure SQL Database.
The fourth is the newest addition to our family called
Azure SQL Data Warehouse, it's built on SQL Database.
So we're using SQL,
Azure SQL Database to improve the core SQL Server features and
the cadence, so we can learn faster and improve faster.
There's so many interesting and compelling on-premise, hybrid, and
cloud scenarios can be supported by SQL Server.
So, let's talk about the SQL Azure Databases.
So, it is a fully managed SQL database service
that lets you focus on your business.
So, you're DBA can focus down on your database applications,
instead of worrying about the cabling and HA,
as much as supporting your core business.
It's a fully compatible with SQL Server 2016 because it is a same
code, and have four nines availability and
a geo-replication restore service for your disaster recovery.
So let's talk about Azure SQL Database service features.
So, in addition to actual core relational database features,
we're running this as a service so
we offer this as a lot of service features.
There are three different performance tiers called the Basic,
Standard, and the Premium.
The only difference are the performance,
that's why we call them performance tiers.
The rest and in terms of business continuity, programming
service area are fully compatible with SQL 2016 and the same across
all the performance tiers, they have the same availability of four nines.
And we support elastic pool across all these performance tiers as well.
So how we measure the sizes of different databases and actually for
you to size your workload is a something a unit coded DTU,
Database Transaction Unit.
Think about this a bonding box for
your database, because the resource utilization for
your database really is the compute, memory and I/ O, right?
That's what a database transaction does.
If you install all these databases on the same physical hardware,
first come first serve, causing noisy neighbor problem.
And the bonding boxes avoid noisy neighbor problem and
you get all the resources you paid for.
And, allow predictable performance and
dynamically scaling your database workload as you need.
So, because we're billing at the highest rate that hour only,
if you workload peaks in that today at the P6 for an hour, for example.
And you'll be actually leave your database there one hour at P6,
you're gonna build that hour,then you can scale it back down, say to
S3, and the rest of 23 hours, you're only going to be build at S3 price.
And even further, in the order to support the SAS applications
because as SAS Server, your server says Android tenants, right?
And a 100 tenants have 100 database as seen this case.
And, not all of them are actually using it at the same time.
We'll give you even better price performance for
you to actually create this 100 database in a elastic pool.
So you'll be paying the collective pool DTU prices but
these 100 database,
as long as collectively, they don't exceed the maximum pool DTU sizes.
And then, you don't actually have to pay out the individual
database site's price.
So for this way is more elastic, and
is on demand without you have to do anything.
And in order to support all these database GODR and
database continuity, we have three different business
continuity features point-in-time restore,
we support all the way up to 35 days point in time restore of your data.
And we just introduced a longtime data retention
that supports your data back up store for up to ten years.
And, for disaster recovery, we have a geo-restore in case a data
center went out and you can restore your data from
pairing data center and to start it up again.
So all of our database, the actual backup, is copied to a pairing data
center which is remote that will prevent for a complete disaster.
And if you have a mission-critical business and
that needs higher availability, you can create active geo-replicas,
up to four of it, in different regions in the world.
You can actually use these replicas to distribute
your read work load for better performance.
We have lots of features, and security and
compliance, where the most is secure, and have most to compliance
certification public cloud of the data service.
From auditing, encryption at rest, and in flight and
row-level security, and a dynamic data masking.
This is all the compliances we got so far, and
we're adding more logos to these slides.
We basically have a most of the important compliance federal and
state government across the world.
And specialized the compliance like FDA certification to run
the database in the public cloud.
Since we're managing the database through the databases service is
through DevOps.
And, we actually learned a lot from how the database works,
how to manage it, and keep it running, and the availability
of four nines across the 30 data centers, units of data basis.
And our team did in a number of sizes.
In our team actually didn't really grow, so
we have to learn how to work smarter.
Anyway, add a lot of intelligence into managing the database as
a service.
Anyway, actually bubbles this up to help you to get performance
automatically use our data scientist and machine learning models
to get a better performance and to reduce the cost.
We also add the intelligent security to help your database
to protect threats and detect vulnerability before it happens.
There are many customers using SQL Azure databases already.
Hopefully, this video will help you have a conversation
with your customers on using SQL Azure databases.
Thank you very much for watching.
[MUSIC]