I'm not sure if I can do it
I'm not sure if I can do it. I'm not sure if I can do it
I'm not sure if I can do it. That's kind of one
hat that I wear. I know all data professionals wear lots of hats
Even developers, I'm sure, wear lots of hats. Those are some things that I'm familiar with
I also manage a few other things. I help with our tech reviews
Basically, when we're working on features or that sort of thing, I bring the customer voice to that
as well as getting feedback and based on what I hear from
events like this or other events or other customers. Then I also work on a small
team where we do some data science and we work on customer
retention. Trying to figure out how and why customers fail and how we can
improve our experience so that people want to show on our platform
That's kind of like if I had to summarize it as briefly as I could
That's a lot. That's a lot. That's a lot. I think it sounds pretty exciting
When you get to interact with the customers, the community members, then you also work very closely
with the product team so you can get feedback and I think that's really great
Anna looks like you have been at Microsoft Office four years, right
You're always programming. How do you do that so far? Boom! I think you're an amazing
expert. That was great, right? Thank you. I think there's no easy way
to do anything. I think being at the right place and right time is important, but at the end of the day
you have to put in the work. You have to learn about our
products, our features. I started at Microsoft in our consulting arm. That's where I got a lot of
hands-on experience with customers. I moved around, moved to the AI engineering team where I was doing a lot of
sort of a similar thing. Then opportunity came around and the SQL Server and SQL
team and this is such a huge platform, such an exciting platform, innovative technology, but
also has such a huge history. It really seems like how could I not go here? I've now been
on this team almost two years and I think it's hopefully somewhere I'll be able to stay for a while
Yeah, I definitely agree. I think when I look at sections of our topics for today's day, it actually
explains what you've learned. I think this topic is really interesting because when I look
back around in 2013 and 2014, it was known as Bingo Radio, not Microsoft
Azure, that's true. Then we had almost like 10-12 services, right? But now we have like tons and tons
There's so much that Azure has to offer and especially in this
pandemic, we have seen many organizations moving to the cloud. So, definitely
a really interesting section. I think if anyone who's watching this, let us know if you have any questions
in the comment section below and stay with us for the next 45 minutes
And Anna, maybe it's time to go ahead and start the session
and let's do it. Awesome. Yeah, let's do it. I'm excited and I actually want to start
around that history that you were mentioning so I think that's kind of a good
lead in. So, what I want to talk about today is really an introduction to
Azure SQL. So, we're going to talk about some early topics. We're going
to dive deep into what to use when. So, we'll talk about each of the deployment
options as well as some use cases and customer scenarios. I have a few demos planned
Apart from taking your deployment options, which we'll talk about, I also want to talk about the
service here. So, we'll talk about things like serverless, hyperscale, business critical, and I have some
demos that hopefully go as planned today. And then, yeah, if there are questions, I know this is
live so I would love to take questions as I can. And I'll also share some information
and content for later if folks have questions and want to follow up with me. Perfect
Awesome. So, I wanted to start with a brief history of Azure
SQL. Like you said, this project has been around for a long time and it all
started, well, it all started on Azure back in 2008 at the
Professional Developers Conference where Ray Augie, he was the chief software architect at the time, he
got on stage and said, I'm announcing what was called Windows Azure for the
first time. And why I like this so much, because this was the slide
he used and, you know, you can kind of see what was front and center, right
Excellent. And we start in front but I just want to give a
presentation. Oh. That's a good one. I was on the news. I've been fairly frank
Here we go. We got it. Always, always something. So, that's my bad. So, on the left
this is Ray Augie. He was the chief software architect at the time and he got on stage
at this conference and said, I'm announcing Windows Azure for the first
time and, you know, now that you can actually see my slide, you can see
what was front and center at the time. So, SQL services was a big part of
launching Red Dog, Project Red Dog, which turned into Windows Azure and now Azure. And
since then, really, Azure SQL has come a long way since then. So, you can see
just a brief history. I won't dive into it, but apart from all the many changes
which Microsoft is infamous for doing, we've added a lot of capabilities along the way
We've even introduced new versions of Azure SQL. Fun fact, in 2015, we actually deployed
a new version of Azure SQL database under the cover, and so
it's called v12. So, that's why when you do, like, a select
version in Azure SQL, you see this 12 dot yada, yada, yada, as opposed to
something that wouldn't be familiar to the SQL server 2019. So, we've really come
a long way, and I like to mention this because we've evolved
as you all have kind of told us what you need in certain situations, and so
that's kind of how we've taken it's a very customer-first approach to evolving our product
So, I'm going to start by giving an overview of what those Azure
SQL deployment options are, and then we'll dive into the use cases and the challenges and the solutions
related to each and maybe any questions that you guys might have
So, the first option is SQL server as a virtual machine, and this is
known as the infrastructure as a service, and the great thing about this
is that it's just SQL server. So, the version you want, you specify
the OS you want, you specify, and you get everything that you would get in SQL server
in Rails. Now, as we move to the right, what I'm going to do
is extract layer. So, let's say you don't want to manage the OS or the
underlying infrastructure that supports your SQL server. Then you can go towards
one of our managed services like Azure SQL Managed Instance. So, what
we've done there is we've extracted away the OS and a lot of
the SQL server from a management and versioning perspective, and you just
get a managed, you just get to manage SQL server. So, in
Azure SQL Managed Instance, you're going to get those instance-built features, which we'll talk more
about, but you're also going to get to take advantage of things like
versionless SQL that you get with a platform as a service or
has type of offerings. And then if you say, you know, I don't need instance-built
features, I don't need to manage SQL server, I just want a database
and I want to take advantage of some of the latest innovations
that we have in this space, whether it's hyperscale, serverless, or some other things we'll talk
about, and that's where Azure SQL Database comes into place. And this is really great for
new or modern applications when you think about taking advantage of some of the skills that the
cloud has to offer. Now, what we're going to do now is we're going to kind of
delve into each of these options and see what challenges might lead you to land into any of
these important options. So, the first one is SQL server and Azure working between. So
imagine this customer scenario. You're a customer, you have, maybe you have some hardware contacts
that are expiring. You need to move to a cloud and you need to move quickly
Or perhaps you're on SQL server 2008 R2, which reached into support a
while ago, but believe it or not, we still have, we still see many of these
that are running in production today. So, maybe you want to deal with
that situation being in an unsupported scenario. Or maybe you leverage a third
party software, which requires access to the OS. And maybe you have some sort of third party solution
but they need access to the OS, they need access to everything related to
SQL server. All these scenarios and challenges are going to lead you to move towards
something like SQL server on an Azure virtual machine. As I mentioned
this is just SQL server. So, you can go to the cloud
with SQL server 2008 R2 running in a 2008 virtual machine. But what you're going to get with
the 2008 example is access to free standard security updates for those servers
So, that's kind of a big deal to be able to have a little bit more
time, a little bit more runway to either upgrade or move to a managed service
for the next several years. Now, the other thing that you're going to get here
is support for Linux. So, if you want to run SQL server on Linux
in Azure, then that's an opportunity for you to do that here
as well. And then, if you take advantage of just the full box
platform that SQL server has to offer with SSAS, SSRS, SSIS, this is really going to be the easiest way for you
to lift and shift up into Azure. And a customer scenario that I really like
is a customer called Altrix. And I like this story because they had about
600 VMs running on Chrome. And for a number of reasons, they decided, you know, we want to
migrate this to the cloud. We're going to use SQL server on Azure virtual
machines. And they're actually able to fail over very easily using a tool called Azure
Site Recovery, these 600 virtual machines to Azure virtual machines. And that was really able to make it
much easier for them to migrate. They were able to migrate in a matter of
a few weeks. And once they migrated, once they got to SQL server and Azure
virtual machine, then they started to evaluate some of the platform as a service
offerings that they could take advantage of, like Azure SQL Managed Instance
And they actually started moving some of their servers to Azure SQL
Managed Instance. So, I think it's a really interesting example of taking a phased
approach to migration. You know, you get into Azure and then you evaluate the
past services. Now, I'm not going to talk a ton about SQL server on VMs for
the rest of this session, but I did want to call out one thing that
you should really be aware of when it comes to what to use when
There's two ways that you can get SQL server on Azure virtual machine
You can either go into the portal and search for a pre-installed or pre-configured
virtual machine which already has the SQL server version that you want installed. Now, if you do that
you're also going to be able to take advantage of some of the capabilities
that we've added to make things easier for you. Like, we're adding whole
wizards on how to set up always on availability groups, still request
for instances. So, we're helping with things like availability. And we're also
helping with some license management and flexibility. But in order to do this on
that, you need a resource provider. But these pre-installed, pre-configured images have resource provider already
Now, if you go into the portal, you deploy an Azure virtual machine, and then you do what
most folks have been doing for SQL server for years. You install
SQL server. If you take that route, there's one more step. I
just don't want you all to forget to take. And that's enabling the resource
provider. And there's basically a SQL iLogic station that you can use. And that's going to allow you to get all
the benefits that you would get from one of these pre-configured images. So, I
definitely recommend at least checking into that. I won't dive into some of these other topics, but you can see there's
a lot of things to consider, but a lot of benefits to consider when you move to
SQL server on an Azure virtual machine. So, that's kind of the IaaS
side of the house, so hyperstructure as a service. And before we move to
PaaS, I just wanted to briefly cover some of the differences between
IaaS and PaaS, and why you might consider moving towards a PaaS service
So, a lot of the things you see on the screen, and I won't go into all of
them, are possible with an IaaS service. The thing is, you know
some of these things take a few extra steps to configure yourself. So, you
have more control, but with more control also comes more responsibility. So, that's kind of the main
trade-off. The other trade-off I would say is as you move towards a
platform as a service, two key things that you get, which is
really awesome in my opinion, are an SLA. So, you get a guaranteed
uptime percentage. So, the highest SLA you can get in Azure SQL
Database today is 99.995%, which amounts to 26 minutes or less of downtime per year. So, that's pretty
significant that you just get just from deploying a certain service during configuration
Now, the other big benefit to a platform as a service is that it's versionless
So, you'll never have to go through an upgrade cycle. Again, you will
always be on the latest and greatest Azure SQL platform that we have, and the
responsibility of not breaking you when upgrades happen falls on us. So, all of that
management and stress and broken scenarios, all that responsibility falls on us
to make sure we keep you running smoothly whether we change things in the back end or not
So, those are a few of the big things, and a lot of these other things, again, the big
indicator is whether or not it's built-in or it's configurable. So, it's just something
to think about. So, for the rest of the session, I want to talk about some of our PAL services
the first one being Azure SQL Managed Instance. Now, this is probably
of all the offerings, maybe the newest deployment option when we think about VMs versus
Database versus Managed Instance, and this one really came around because customers and
developers like yourself were wanting to move to something like Azure SQL
Database, but they actually needed some of those instance scope features. So, when I talk about instance scope features, just to name
a few of what I'm talking about, I'm talking about Service Broker, SQL Server
Agent, CLR, Machine Learning Services, VCT now, these are all things that are instance scope
features that you can't get in Azure SQL Database today, but you
can get in Azure SQL Managed Instance. So, sometimes when we talk
about this, we like to say that in Azure SQL Managed Instance, you're getting the
best of SQL Server with the best of a managed service, so you're kind of able to
get all the features you might want, but also take advantage of some of the things
I was mentioning, like an SLA and versionless type of SQL. You can see there are some other things that
we do here to help you. We actually have native virtual network support. We deploy a whole
virtual cluster for you when you deploy Azure SQL Managed Instance. You can really
use this as an extension of your on-premises network, if that's what
you decide to do. We have some other financial benefits that I'll provide links to, if you
want to read into the trade-off between what's really more expensive when it comes to running on-prem versus
running in Azure SQL Managed Instance. And, talking about Torii, I really like it for Masi, because
they were able to very smoothly, very quickly, migrate to Azure SQL Managed Instance from
SQL Server on-prem. And those numbers that you see, you know, 49
cost reduction and 25-30% performance gain, those are pretty significant, you know
either reduction in cost and increase in performance. So, this is great, and we just keep adding
to this thing. The goodness just keeps getting better. We just announced some things
to make this run at an even higher level of performance and no changes to cost to you
That came through in October, so something to check out, as well as DPP
We just announced DPP very, very recently, and this was a big customer ask, so I
think many people might be excited about that. So, like Azure SQL Managed Instance, so remember, it's like
a managed SQL Server. You're getting those instance scope features, like I mentioned
Now, if you don't need those instance scope features and you want to, you know, take advantage of
some other things, then Azure SQL Database might be the right solution for you
Now, there are many customer challenges that would lead a customer to
picking Azure SQL Database, so I'm just going to name a few of them
So, one could be that you run a multi-tenanted service, and you want a way to
resource share and cost optimize between these databases that you might have
through your different clients. Azure SQL Database and lots of tools is going to allow you to do that
So, that's one example. Another example is perhaps you have a database
that is bigger than 8 terabytes in size, and only in this deployment
offering are you going to get access to something called Hyperscale, which is
going to allow you to basically get unlimited storage, so that's a big benefit as
well. We also have support for serverless, which I'll talk about actually on the demo for later
And, you know, it's really just going to get you a managed
database service. You can get to developing your applications as quickly as possible
And speaking of developing applications, I know that there's a lot of developers that watch this show
We are actually putting out a book. We're in the final stages. You can find
the book on APRESS now, and it's called Practical Azure SQL for Developers. So, if you're
watching this and you're a little bit new to Azure SQL Database and you're
trying to figure out, okay, how can I build new applications with that, I definitely
recommend that book that we're putting out. I think it will be released
shortly, but you can go ahead and pre-order it. So, that's just
a little teamwork squad I'm going to throw in there. So, we're going to talk a lot
more about some of these options that are available in Azure SQL Database, but one
customer example, just to kick it off, is AccuWeather. And I like this customer
example because they were really trying to take advantage of the full Azure
platform. So, they wanted an Azure SQL Database that they could just
get to developing, not worry about the instance, and connect to other services
very easily, like Azure machine learning services, or things like Azure Data Factories
or data orchestration. So, they were able to very easily piece these things together, build
a new intelligent application for helping with prediction services related to customers in the
AccuWeather service prediction space. Okay, so we've talked about the different performance
offerings, and so you might say, okay, I totally get it, but some of you might be saying, okay
can you break this down into a decision tree for me? And this
is something we've heard a lot from folks that would like to see a decision tree. It's hard
to do that because, as we all know in the software space, the classic answer is
really, it depends. And so, what we have come up with this thing to maybe help that
make that a little bit easier, and really you think about it in two
ways, control and capability. So, these are kind of your driving reasons for
what decision or what offering you might, might be best for your
application. Now, if you want a customer managed, so you want to manage your service
and you want full control of the SQL Server instance, which we talked about, then
the best option for you is probably going to be SQL Server and Azure Virtual Machine. Now, this isn't
like the law, you know, there are exceptions to all these things
but generally this is the direction we see folks going. Now, we say, you know, you don't need those
capabilities like OS level access, the SQL Server versions, or these app or other services
with access to that OS. If you don't need that, then you're more conducive to
running in a Microsoft managed type of service. And your options here are first, if you want
a fully managed SQL Server instance. So, if you need some of these things like
root server, cross-database transactions, I talked about some of these ancient scope capabilities
Now, if you need any of those, or you think you'll need or want them in the future
then Azure SQL Managed Instance is going to be the best place
for you to land. And finally, if you don't need any of those things, and you don't need the
SQL Server version, then you can kind of just land on a database scope programming model
which leads you to Azure SQL Database. So, this is a very
simple decision tree. There are exceptions. We're going to talk about some of the reasons you might consider one
versus the other. But hopefully this kind of helps bring things home for
folks. You know, I wanted to check in, Simon. How's it going? Do we have
any questions? I just saw your presentation, I think, for the entire ecosystem
that you have been covering from the very beginning, right, from the very beginning
There are a couple of questions coming from the viewers. One is by a friend who says
can you take a current license to Azure SQL on VX? Yes, that
is a great question. Thanks for asking that question. In fact, you can
take your existing licenses and move them to SQL Server on an Azure virtual machine
There's actually some license flexibility that's available for that. Some really interesting
ways to get more out of your license on-prem if you move some of it into Azure or you start
leveraging some combinations. So, yes, the answer is yes, definitely, if you move to SQL Server
as a virtual machine. And even if you have an existing SQL Server license
and you move to a past service like Azure SQL Database or Azure SQL Managed Instance, you can
also get really large savings with that existing license. It's called Azure Hybrid
Benefit. So, great question. The answer is 100% yes. I can definitely
share some more resources in the chat after this session. But, yes, a great question
and thank you for bringing it up. Yeah, and I think this is one of the questions
coming from my peers. If you can just go ahead and type it in, it will break out
Yeah, what was the name of the book I got? Oh, I'm excited for someone to
know the name of the book. That's very helpful. The name of the book is
Practical Azure SQL Database for Developing I think that's it. I will also put a link to that
There is a short link. I'll share it with you. I'm sending that to you
Simon, if you want to add that to our chat. And that's where
you can kind of go ahead and pre-order the book. I think that's the link to Amazon
But we're really excited about the book. I've gotten to work with some really
smart people like Divite Marmi, Silvano, I'm going to butcher his last name
Koryani, and Jillian Popovich, as well as Faheem Mishra. So, we all worked together to write this book
It's really amazing. I actually learned a lot while writing the book. So
definitely check that out. You're welcome. We can take one more question
Maybe after, if you want to take one question now. Yeah, we can take one more
Could you please thank you, miss, on how pricing works for these different SQL options
Yeah, definitely. I can spend just a brief moment here, and then I can also
as we go one level deeper, you'll kind of see some more comparisons, because
while it depends at this level, it depends more at one level
lower when you talk about using Serverless or HyperSQL or that sort of thing
So, at the highest level when you look at people to run Azure
Virtual Machine, you can use your existing license, and it's going to transfer
the same sort of way, except you're also going to have to pay for the
VM virtual machine running underneath, of course, the compute that you're using
there as opposed to in your on-prem environment. There's also options for pay-as-you-go for
SQL Server on Azure Virtual Machine if your license expires or that sort of thing
For Azure SQL Managed Instance, I mentioned Azure Hybrid Benefit, as well
for Azure SQL Database, you can leverage Azure Hybrid Benefit to get, I think
like a 55% cost savings with your existing licenses. And then, you also have things like
reserve capacity. So, reserve capacity is the ability to basically pre-pay, maybe
you pre-pay for like three years in advance, but because you're pre-paying
or pre-committing to a certain level, you actually get a significant discount. And then
at a more granular level, it really just depends on the compute and storage requirements that you
need. And same with your backup sort of redundancy system that you
want to lay out. So, really, there's a big itch to fix here
We do have some pricing calculators online, which I can share with you after
this. I can put them in a chat so you can really explore the details. But I think
in this next section, you'll learn more about the pricing and have a better understanding
of like which options to use from a costing perspective if your scenario allows
for that sort of thing. So, hopefully, that will help answer your questions. So, my
short answer is the station unit and my other short answer is the system
Yeah, I mean, definitely, you did mention the pricing cycle. It's really amazing, right? Because I mean, I
think you've been using it a lot and getting an idea of how much this will be expensive and then a lot of it
moves throughout your... I guess I'm just really excited for the second half and I'm
a lot of people who didn't get started for the second half. We have many more questions coming more, so
we'll answer at the end of that. Sounds great. Thanks, Simon. Okay, so
we talked about the deployment options and now that we're seeing this, this
generates a lot of questions and you do have some tools which you can use in your own
environment to kind of evaluate where you might want to land. One tool is called the Data Migration
Assistance or DMA. So, I highly recommend doing a search for this service and
basically what it will do is it will scan your SQL Server instance and tell
you, you know, if you want to move to managed instance, is it good or
are there a few things you might need to consider before you actually move there or
then say thank you database or even an upgrade within SQL Server. So, that can be a really great tool
So, what we're going to do now is we're going to shift and say, okay, if I pick
Azure SQL Managed Instance or Azure SQL Database, what's the next big choice that I have to make
And that next big choice is really about around the service here. But for Azure SQL
Database, you do have one more option that's available and that is the
purchasing model. Now, this is only available for Azure SQL Database because this service has been around for
many, many years, 10 plus years. So, we do have two different models. The VPU model, which
you see on the left, is kind of our legacy model and what
this was is a way to give you a prepackaged bundle of compute and storage
So, you just scale off your VPU up or down and you get more compute
and storage. Now, this is great. It offers the simplicity of choice
but what we heard from many customers is like, you know, I'd actually like to
be able to independently scale my compute and storage. And maybe I need a lot of compute but not a lot of
storage or vice versa or some combination in between. So, maybe a few years back
we came out with the vCore model, which allows you to do this
This is our recommendation for two reasons, some which I've already touched on
One, this is the only purchasing model that allows you to take advantage of things like
Azure Hybrid Benefit and Reserve Capacity. So, if you're looking for savings or you have an existing license
the vCore model kind of opens more doors for those opportunities, whereas these
options aren't available in the VPU model. And then, you know, this is also great
because this is the only option you're going to have available for services
like serverless, which you probably heard a lot about and we're going to talk more about
later. But this is kind of our recommendation. Now, of course, there are exceptions
to this. If you just need a really small database with a really small
workload, you can actually get sub-core databases in the VPU model. So, if you need
that sort of thing, then maybe the VPU model is going to be better for you
But for the rest of this session, we're going to talk about the services that are
available in the vCore model. And we'll talk about these across SQL Database and
SQL Managed Instance because in Azure SQL Managed Instance, yes, they don't have the VPU option. You
only have the vCore option. So, with that being said, let's talk about the
three main services for SQL Database and kind of for management and software in the
Azure Azure. So, the first service here is General Purpose. And this is best
for, as the name suggests, most business workloads. So, most of our customers are running on General Purpose
today, and it's just fine for what their application needs. You're going to see, I'm
going to go through some of the details here related to kind of architectures
and the performance that you're going to get so that you can compare
and contrast these different offerings. So, just stay tuned with me on this one, but basically you just
have one primary and your data and log files are stored in Azure Premium
Storage. Your 10TB is on directly attached SSD, but your data and log
files is in Azure Premium Storage. So, that could introduce a little bit of latency
Now, if that is unexpectable to you or you have some sort of
mission critical application which really needs the low latency fast failover, Business
Critical might be a better option for you. If you're familiar with
SQL Server, older versions, and the way availability works, the difference between
General Purpose and Business Critical, if you think about it, is General Purpose is
run more like a failover cluster instance, if you're familiar with those
That's why you just see the one primary and then you kind of have this idea of
shared storage. So, when we fail you over, we have to look for a
node, there's Cassie, we can figure out all the connections, and this can take some
time. We'll see actually in a demo how it actually doesn't take that much time
but this takes some time. So, if you need something better than that, with Business
Critical, what we do is behind the scenes we deploy it always on availability proof
So, that's why you also see down at the bottom, those are my representations
of what it looks like, but you have your primary, and you actually have three
secondary replicas, one of them which you can use for read skill
So, this is going to help you with read skill, as with that you have a readable replica
but on top of that, when you have to fail over, since we already kind of have these secondary
TNE5, we can fail you over much faster. I've seen this take
between two and eight seconds. So, if that's something you need, then Business Critical might be
a good selection for service peers. Additionally, in-memory LLTT is only supported in the Business
Critical service peer, so again, if your application requires something like this or could take advantage of something
like this, it might be a reason that you've moved towards Business Critical
Now, the general purpose service peer is the only service peer today that
allows for this idea of a serverless application, which we'll talk about, but I just wanted to mention
that since you see it on the screen, you're probably wondering. Also, there's this
thing called IOPS, or IO per second, and I use kind of a
comparative analogy to compare the two things. You can see, you can get much better
IOPS in Business Critical, but you can also see you're going to pay
a price for that, right? Business Critical is in my opinion, significantly
more expensive if you do it on purpose, but it might meet
the needs that your business has. Now, the third service peer I wanted to mention, which is only related
to Azure SQL Database today, at least, is Hyperscale. Hyperscale is really interesting
In fact, we could have a whole session dedicated to how interesting Hyperscale is
because we basically re-architected SQL Server for the cloud. We implemented this really interesting
task layering system, which allows us to remove silent data operations and make them constant time operations
which is really powerful, and also gets you above the 8 terabyte limit that you see today
in some of our offerings. You can have up to 100 terabytes, and in theory
that's just a number. There's nothing in our architecture stopping you from
going bigger than 100 terabytes. One of the other interesting things you can
see is that you can deploy 0 to 4 readable replicas, so that's not only going to
help you with availability, but also with things like read scale. Another interesting thing, you could
have 0, in which case your scaleover would be more like general purpose, but you
could have up to 4. Now I thought it would be an interesting time
to take a break from the slides and take a look at the demo
I'm also going to hide this. We'll also take a look at how this works in practice
What I have here, if you just give me a second to set this up, is
this is Agilent Data Studio. For all the developers out there, Agilent Data Studio was built on a fork
of VS Code, so if it looks kind of like VS Code, that's why
I love Agilent Data Studio on a big scan. One of the things
I really like is this idea of notebooks. All the data science
shows their similarities, but basically the Agilent Data team added the SQL kernel to
the Jupyter notebook, and also we have a PowerShell kernel, which is the one I find myself using the most
often. The wonderful thing about this is that it allows you to basically mix text cells
and code cells, and unlike Jupyter, it actually makes writing markdown really easy
You see I have all the editors that I get elsewhere. That's just a side point
Anyways, let's talk about what's happening. I have Agilent Data Studio. I've got
two notebooks, one on the right, as well as a PowerShell window on the right
If we just talk about what I'm doing on the right side, what I have is I have
a business-critical database. Let me just make sure that I am connected to that properly
What I have is I have a business-critical database. Again, that's why I'm always on
availability if you're behind the scenes. We're going to try to force this day over
and see how long it takes. We'll see if the demo lock is in my favor today, but
usually it takes between two and eight seconds. Then down on the right, what we have is
we have this OSTRECH workload. The OSTRECH workload is basically ... I'm going to cancel it
This OSTRECH workload ... Let me make that easier for you guys. ..
You can compare it with this one, too. I have these two OSTRECH workloads. If you haven't
seen OSTRECH before, it's a really great tool for creating a workload
simulating a workload. What I'm doing is I'm connecting to this business-critical database
which had InventorWorks deployed. I'm just doing a simple select count from a table, just so we
can query if the database is able to connect to or not
What you'll notice on the left side is I have the same database and query, except
this is a general-purpose database. There are two different databases deployed, but they kind of have the same
data in them and have the same query on them. That's why when
you run both of them, you see the 847 result being returned
This is just saying, is that database available or not? I'm also going to invoke a failover at the
same time on a general-purpose database. We'll compare how these failovers occur
Remember, right side is business-critical, left side is general-purpose. Right side is always on availability groups
left side is FBI failover cluster instance. Let's hope this works. Almost immediately
what we saw is the business-critical database became unavailable. Pretty soon after that
the general-purpose database also became unavailable. Usually, or what we would hopefully hope
to see, is that the business-critical and as you can see, it has
The business-critical database fails over and becomes available much faster. Before I could even really finish explaining
what had happened. The reason for this is because it has an always-on availability group behind the scenes
we're simply having to redirect those pointers to get you to a
secondary and then go back up to up and running. We take care of all the redirection
in the background. Just another side comment, it's really important to have retry logic
built into your application. You would never want some little blip like this
to actually cause you to go down. Especially when it's just for such a short
amount of time. What you can see with general-purpose is we were also able to fail
over very quickly. I think it was probably around 25 seconds that it
took to do that. The reason it took a little bit longer is because
it is, we only have one primary. We are having to look for a node, fill you over
to that, read the cloud-specific data and log files and then update your
connector. It just takes a little bit longer. I really love this demo because
at the end of the day, what we're showing is that the power of platform as a service
Remember, I didn't do anything special here. I deployed a business critical database and I deployed a general-purpose
database. I didn't set up an availability group, I didn't set up
scale over corporations, I didn't do anything funky or special. It's just the deployment, what you get
I think that's pretty cool to see the type of availability you get out
of the box without any headaches, without doing anything in Azure SQL
platform as a service. This was on Azure SQL database, but you would see
the same behavior in an Azure SQL managed instance. Awesome. We've talked
about the service here and you've seen the differences between general-purpose and
business-critical. Hyperscale, depending on the number of replicas, behaves more like general-purpose
or more like business-critical. Hopefully, this gives you an idea of what to use when and also
the comparative use of pricing as well as IO per second, as well as some other benefits
that are there to help you decide what might be the best for your workload
There's one thing I didn't really talk about yet, which I want to
and that is serverless. To be clear, serverless today is only available in Azure
SQL database, so not managed instance, and it's only available in the general-purpose service here
Let's talk about what it is and why it might be good
for your scenario. I want to do that by taking an example application
Let's say I work at a company and we have a line of business
expense reporting application. This application gets unpredictable usage. Most weeks, it doesn't get a ton of usage, but then
sometimes near the end of the month, there's spikes in demand. We have this unpredictable usage pattern
and in addition to that, on the weekends or at night, maybe between the hours of
7 p.m. and 7 a.m., no one touches this database, so it's really less
unused. This is a great scenario for serverless because what you can do is you can
set the minimum and the maximum number of records, and then what we can do is
fill you and scale you, auto-scale you on a per-second basis for the amount of cores
that you actually need for your workload. We can scale you up to, in this example
you're going from one to four records. We can scale you up to four records, and then we
can bring you back down once your workload is complete. After a period
in activity, you can actually pause your database. You don't have to configure autopause
but you can pause your database, and during that pause time, people's serverless
and storage shut down, and your compute and storage are separate, so you're only going to be billed for storage
at that time. I think it's a really interesting scenario. We're seeing a lot
of uptakes on this particular scenario and this service, so I thought it would be cool
to show you a little demo of how this works. I'm going to go ahead
and switch over to that. We should be good. What you can
see here is I have a serverless database, and you can also see the total CPU
usage seconds is currently zero for most of those cores because I haven't
used them. I haven't been using them. Now, I can create a workload, so I'm using
OSHA again to create a workload, and what we can do is we can use this query
again, and what we're going to start to see is the total CPU usage
seconds is going to go up. Now, this is how I'm billed, so we can
see this is going up, and what's happening here is serverless is auto-scaling up to the number
of these cores that we need and only billing us for that
We can see that this workload takes a little bit to complete, but really, at the end of the
day, we're only going to be billed for the CPU we actually use
Now, after this workload completes, we have a really interesting way of bringing you back
down, so we have this interesting task reclamation system to bring your
massive memory back down so that we can start you off. If we take a look at the portal
what I've done is I've also set up an auto-pause delay of one hour, which means after
one hour of inactivity, no connecting to the database, this will shut off
and so what that allows me to do is only be billed for the CPU
that I actually need, so you can see it varies as opposed to being
billed at the set CPU regardless of whether or not I use it
I'm only billed for what I use. When I don't use it, I'm not billed at all. I can even look
at the past 24 hours, and you can take a look and see
you can actually see that task reclamation system in progress with that CPU bill
This is very interesting, really innovative technology that we're doing. I hope that was interesting, and I'll
share more information if you want to. I'll learn more about how
I set that up or try it for yourself, but this is really an innovative space
I think for us, and so maybe hope to see more innovation in this space
in the future. We kind of talked about the big things as far as what to use when. We talked about
the deployment options, and we also talked about the service peers, which I
think are some of the biggest choices you have to make when it comes to deploying
something in Azure SQL. I did want to briefly mention some of the ways
that we're allowing you to work with Azure SQL. A lot of them
are the same as what you're used to for SQL Server, or if you are
an Azure person developing in Azure, we have really nice interfaces in Azure, which I'll show you in a moment
SQL Server Management Studio is going to work for all Azure SQL, whether it's on-prem or in the
cloud, so that's nice to just keep using SSMS, and for all
you devs out there on Mac and Linux, I myself have a Mac device as well, and
SSMS does not run on Mac, as you know, but Azure Data Studio
which you saw off your Windows, does work on Linux and Mac, so this is really
great. It's also really innovative and soft with the PowerShell notebooks that
are there. You can use that to connect to your databases as you're developing
And then we also have a slew of command line tools and REST APIs
for you to use to, whether it's load data, querying data, you know
systems in SQL that you're familiar with from SQL Server, and we have
some new tools if you're newer to Azure, like Azure PowerShell and Azure CLI
which really makes managing these things very easy and scriptable and repeatable. What you saw
in the demo was Azure PowerShell, but there are very similar things
you can do using Azure CLI. Alright, so I have I think this is my last demo
and what this is, is a gist of the Azure portal. So I wanted to show you how
we're kind of trying to make it easier for you to make these what-to-use-when types
of decisions. So what I'm going to do is I'm going to go ahead and click Azure
SQL. Now, if you don't have that tab up there, you can just search for Azure SQL
in the portal, and then select the Azure SQL services that will bring you to the
same place. Now, I'm just going to look at one subscription so
you can see. But what you can see is this kind of gives me
one pane of glass to see all of my SQL resources. So
whether or not, regardless of search here, if it's a SQL database
or SQL maintenance, I'll be able to see it. I'll also be able to
see things like my logical SQL Server. I can even see my SQL virtual machines and see
what is running. So Enterprise SQL Server and Windows Server 19. And I can
see if I'm running developer additions. You can see there's lots of things that you can
see all from one place. So this is really interesting. Certainly helps in
cutting down on finding new resources. Reservations is where you can manage that thing I was talking
about, reserve capacity. So you can manage your reservations here or you can see the things that stay on the
end call. Now if I want to add a new resource, we're also
trying to support this Azure SQL use when by giving you options here and talking
about some of those options. So in Azure SQL database, what are your choices
In manage instance, what are your choices in Azure SQL virtual machine? What are your choices? And maybe the best
thing about this new UI is I don't know if you ever tried to find a SQL
Server VM before in the Azure Marketplace, but we've got them all
right here. Whether you're running on Suze or REL, we have those images
here based on your license, based on the type of addition. And if you go all the way
down, you can even find Google Server 2008 R2 SP3 on Windows Server 2008 R2
So we really have all these images available for you to go ahead and
start taking a look at some of those things that Google Server VM provides
for you. So that was kind of a lot to get through in
not a lot of time, but I really hope that what you walk away
with is some clarity around virtual machines, first managed instance, first single database
as well as less of a feeling of confusion and overwhelmedness related to all these different choices that
are available, and more seeing it as the flexibility that the platform has for you. So if
you have a serverless type of workload, or a hyper-slow workload, or you really just
need Google Server as a virtual machine, Azure SQL has these offerings for you
Satya says that, Satya, our CEO at Microsoft, he says that Azure should be the
world's computer, right? And we believe that Azure SQL has evolved over the years to
be the world's database. And I know that's a little corny, but
that's kind of how we feel. And then, finally, I wanted to share
some resources, tons of resources. I mentioned that I do a lot of content development
One thing that I released recently I wanted to share with you is
a learning path on Microsoft Learn called Azure SQL Fundamentals. We actually covered today
what would be in module one, instructions to Azure SQL. But you can see
there's also things about deploy and configure, security, performance, availability, and how you combine all these
things into a solution. So there's really a lot here, and one of the awesome
things about Microsoft Learn is that if you go into any of the exercises, there's actually
a built-in sandbox. So you can see I have a sandbox today
and I'll have two and a half hours left, and I can use 18 more today
So what is a sandbox? A sandbox is going to allow you to
deploy resources for free for a certain amount of time. So if I click
this, I already have it open. You can see I have this Microsoft Learn sandbox
where I can actually go in and say, oh, you know, I actually want to
create this, and just to show you what it might look like, if I can
actually go through this, it gives me a subscription. So this isn't any of my
normal subscriptions. It gives me a resource group, and I can actually deploy things in here
if I fill them out. So that's kind of a great way to get hands-on
and get started with Azure SQL. The other thing is we have resources on GitHub, so if you want to
see some pretty gnarly labs, those are on GitHub as well, as well as slides for the whole
workshop. They're all on GitHub, so if you want to take them and use them
for your own learning or for teaching other people, we would love that. All this stuff is
open-source, so we'd love for you to reuse it. This is a learning path I was
talking about. Our documentation is actually really good, so I recommend whenever you're confused
just do a search for Azure SQL Docs plus whatever it is you're looking
for. So Azure SQL Docs Availability Group, something like that. And then some
shameless plugs for more videos. Bob, Ward, and myself did a 61-video series called Azure
SQL for Beginners. It's these really short videos where you can learn more
about Azure SQL. And then Data Exposed is the show that I host on YouTube
that Simon mentioned earlier in the talk. So if you want to learn more, we just agree to
MVP's, we get programming anywhere on the show, and you learn about what they're doing
demos of what they're doing. So lots of awesome resources. If you want this
deck, you can find it on my GitHub if you look up ms-analytics
And feel free to follow Azure SQL, you can hashtag Azure SQL
and you can follow me on Twitter, or you can just message me on Twitter if you have any questions
I do want to make myself available to help. So Simon, you know, is your
heart fluttering? Or do you think it's a new topic? Oh my goodness, Raina, what an amazing
slides and demos you had. I think it was an incredible session
last 35 minutes. One thing, I mean, most of the things really went over my head, because
I didn't understand much of your stuff, but one thing I really loved is, I think
people using Jupyter Notebooks on that for the Python stuff, because that's what
I used to do. But you know, you did it for the SQL things, right
So did you use any particular extension, or what it seemed like
Jupyter Notebooks, or any other extension that you would like to go and update something for the dashboard
Yeah, that's a great comment. And as someone who came from the data
science world, into the SQL world, kind of not knowing anything about this
seeing Jupyter Notebooks come into the picture here was awesome, because, you know, I love
Jupyter Notebooks, I think you all know you love Jupyter Notebooks, a lot of people love Jupyter Notebooks
and to see the data platforms behind that was exciting. So actually what happened
is, our team developed the SQL kernel, which allows you to interact using
SQL, and we committed it back into Open Source Jupyter. So it is available in Jupyter today
You can also get it built in, in Azure Data Studio, and similar, we've done a similar
thing with the PowerShell kernel, which before I don't think was available
in Jupyter. So I don't think you need any specific extension, if you
go to, if you use Azure Data Studio, you can get it
by default. I know in Python there is a PowerShell kernel, I think it's
called PowerShell-kernel, but yeah, I think it's an awesome tool and it's nice to see the
data platform community kind of take it on and use it for what makes sense to them, similar to how the
Python folks have done. Yeah, I think what I've seen in some of the demos is like, you can do
all this stuff also within the Visual Studio code, right? You don't have to go and create a
resource in Azure. You can go to Portraits, you can log into your subscription for Visual Studio
code, create a resource, and you can use it to deploy two different databases from
Visual Studio code, which is fantastic. So, let's, it's time to go ahead
and take these questions I know we have been getting for a while now
So let's take questions coming from Manish Gide, he says, we have 50
GB database and planning to move on Azure VM. What would you suggest
XSquare servers on VM or manage XSquare Azure, for instance? Awesome. Thank you, Manish, that's
a great question. So, if it's a 50 GB database, it really, you know, it really just
depends on what you're actually using this database for. You know, are you using things like
SQL Server Agents, are you using things like Service Broker, CLR, those sort of instance-built
features. But, if you aren't using those instance-built features, you might be very well set up
to move to Azure SQL database. But, if you need access to the OAuth in this VM
that you're talking about, then SQL Server and Azure Virtual Machine could be
the best option. So, what my advice to you would be is to
download the data migration assistant, and I couldn't find a name for that and include it. But, basically
download that and run it on your, the same machine where your 50 GB database is
and see if moving to Azure SQL Managed Instance, like you said
introduces any blockers for you. And, if it does, then you can
kind of go from there. It's hard to say, you know, just with this
information, what might be the best option for you. But, I would say
like more and more moving towards a managed service like Azure SQL Managed Instance
or Azure SQL Database, if you can, without too much headache, it's going to be best for the long run, because
you'll never have to upgrade again. You're just kind of set up and you have an SLA
and many of the other advantages I talked about you can get in things like
Managed Instance and Database. Yeah, and I think that would be great
if that were the case, right? You get the 26 levels on time, right
Yeah, so if you're in Azure SQL Database business critical, you can get a 99.995
SLA, which means 26 minutes or less a year. And, if we don't meet that, then you get
some service credit back. So, we're really putting our money where our mouth is, actually. Yeah
So, next question, and you're a program manager, right? So, maybe you can answer
the next title. Can you have a dedicated session on the hardship skills from
Chinese people? Oh, that's a request for Chinese coming in. I think that might be a question for you, Simon
I do think, you know, it would be an awesome session. And I think
there might be a few sessions that if you search around, you might be able to find one
I know upcoming at PaaS Summit, which might be an event you all have heard of. At PaaS Summit
Bob Ward and Giselle Ribeiro are doing an ultra deep dive on the HyperSQL architecture
So, if you are seeing that, that might be something to check out
But, yeah, I think that would be a great session. And, Simon, I can give you a recommendation
for someone if you want to go out and have a look
That's absolutely great. It looks like people are really loving this session. They're getting a lot
more coming from your team. So, yeah, definitely just follow the link
And I see you mentioned Bob. It looks like we did have Bob in one of our virtual
conferences. It was like a virtual conference, right? So, yeah. We did have two guys in our..
I think two guys in our conference. That was really great. Yeah, it was
I actually got their shirt, which you can't really see. Oh! Oh, my goodness
Oh, yeah. That's great. You kept on. Perfect. I think I got this after the Light Up
conference. Yeah. Perfect. So, this is the last time. I think we should be doing
the other day, too. So, should be going to do a couple of days
or so, maybe. I think we are coming. So, when you have
that opportunity, Kate, what is the external version of Azure SQL? Yeah, that's a great question
So, really, what we say is Azure SQL, when we talk about
Azure SQL Managed Instance and Azure SQL Database, it is versionless. So, basically, what happens
is we have this SQL Server engine code, right? And what you'll see
is for, like, for example, SQL Server 2019, there's different CUs which have different
or similar updates which have different versions of the engine, right? And as you move through CU, you get the newer
version of the engine. So, with Azure SQL, we usually have that same engine
the same engine code base, except what we're able to do, since we
are not making you upgrade or that sort of thing, we're able to
kind of, as we update the engine and add new features, we can push
them to you immediately. So, there isn't, per se, like a version
to these platform as a service capabilities because you're basically always up to date
So, that's something you no longer really have to worry about. But, I mean, the interesting
is if you do do a select add version on an Azure SQL Database, you'll
get returned something like 12 point something, which might not make you think it's the latest version of SQL
but it is. It just refers to that v12 architecture which I mentioned
we deployed some time back. Yeah, and I'm excited for that video
I just didn't go deep in. Yeah, it's an awesome show. I also
have this. You know, I'm not outside, so I'm not wearing it
Oh, you've got the mask too? Oh my goodness. These are corner masks
so I'm like all decked out. Yeah, you're a bandit today. I'm good
All right, so I guess at this point, we'll just take a couple of more questions
while you're at it. I think maybe you want to go write an ad or something
We have a question asking, SQL model charges EICR separately and it matches the stream
of V2. What's the advantage of SQL? Yeah, sure. I think that's
a great question. If I understand it correctly, you're talking about when you
do a point-in-time restore, which I exactly understand, but I can give a few comments. Basically
point-in-time restore, for those of you that are new, is this ability that SQL Server
and Azure SQL has. It can manage all your backup for you
in Azure SQL database and manage instance. We can allow you to basically
do a point-in-time restore to sometime previously. You can even restore a deleted
database, so it's a really awesome capability. There is a pricing difference between vCore
point-in-time restore and VCU. I'm not exactly sure what that price difference
is, so I might have to follow up offline. As I was
mentioning, there are lots of advantages to the vCore model, such as around
pricing. You can get Azure Hybrid Benefit. Maybe you can't get this point-in-time restore thing. I'm not sure about
that. You can get Azure Hybrid Benefit, where you can pay, I think, up
to 55% if you have an existing license. You can also take advantage
of reverse capacity, which we talked about. You can also take advantage
of things that just aren't available in the VCU model. So, Hyperscale
is not available in the VCU model. Serverless is not available in the VCU
model. Azure SQL manage instance isn't available in the VCU model. Those are a few reasons why you might
choose vCore over VCU. I'd be happy to follow up offline about that specific
pricing question. I'm just not sure. Yeah, I'm really impressed. It's pretty impressive to have
an existing SQL sub-kit chain. We get some of the big sounds on the Azure. That's pretty impressive. I'm not
sure how many people know that, but that's really cool to know. We have
a couple of more questions. I know there's a lot of questions coming in
They're coming from our private channel, C-Sharp and our groups. We have one
Oh, my goodness. This is stupid. I just changed the bandwidth. It says, hello, I have a mobile game
running on C-Sharp server, which is a console app and virtual machine
For this annual database, I'm confused on which of the options to choose
Are there some advantages or disadvantages on VM apps to communicate with
each of the points? That's interesting. That's a great question. Again, it's going to depend on your
business application. What I would say is from a connection standpoint for C-Sharp, you're going to
use the same driver, SQL server versus Azure SQL. That's something that's
available. If your console app is running on an Azure virtual machine, then there could be some
benefits to using any of the Azure SQL services. Maybe Azure SQL database could be
the easiest and the lightest database for you to leverage. They even have really small databases
in the GPU model, which are only $5 a month. If you're doing a small project
or you're just doing some dev tests, you could try that. Additionally, some benefits that you get
just running these things in the same location or the same virtual network
group is just cutting down on that latency. If you have this console app running on an Azure virtual
machine, but you have a SQL server database on-prem, obviously that's going to increase some latency
you might want to avoid. It is going on an Azure. It's really interesting
that if you just want to go ahead and test this out, Azure gives you a free
account for almost $200 maybe. Why don't you just go ahead and use it and test
around it. I mean, this console app, I think it should do just the task
for you, right? Yeah, so there's that and there's also you could use
the Azure SQL fundamentals which I showed on Microsoft Learn. If you're just doing some short-term testing
as a small database, that's all free and you can do that as many times as you want
So that's an option as well. Yeah, talking about free, we have
Manish, you said is DMA free? Yes, DMA is free. Let me find that
link. Data migration assistant. So DMA is free and also if you choose
to migrate to, let's see, often a link shows up for that
But if you choose to do DMA and you want to migrate
we also have a service called Azure Database Migration Service which can actually help you with the migration as well
and this is free. Even the premium tier, so what users, you know, more compute
fastly migrate you to any of the Azure SQL deployment options is free for the first six
months and hopefully your migration doesn't take any longer than that. So really, it's just a free
service to help you get migrated. So there's a lot of tools. The one
resource I'll just share with you Simon is datahydration.microsoft.com That's a resource that you can
use to basically pick your source and your target and you'll get a custom guide. So you could say
I'm moving from Oracle to Azure SQL Database and we'll give you a custom
guide on how to go through that migration journey. That's perfect. You said you have a lot of
resources to share, right? Coming from the DMA demo slides, you're saying
So we did find some questions coming from one of the MC. Let me find this
so I can go ahead and pick one. Alright. Okay, so you know that
I mean, Azure comes with a million things to invite you to go ahead
and create some alerts. The question is what are some of the best practices of
creating alerts? Oh yeah, that's a loaded question. You know, there's a lot of answers that
people might give you for this. I would say like, you know
if you're familiar with Azure platform as it seems like the person asking this question
probably is, there are lots of ways that you can set up alerts
whether it's in the Azure portal, using some of the CLI tools
or just using things like triggers, Azure functions. I know like personally for myself, like
I use Logic Apps for some things and I use the standard Azure Alerts for other things
So really just even Azure functions I use for certain triggers to do other things
if I want a little more control over what I'm doing. So not a great answer
I was just saying, it depends on what you're trying to do
That depends on the customer too, right? It depends on the customer, their data, what they have
That's up to your scenario, right? So here's a question that is related to you
Which kind do you prefer, Azure CLI or Azure PowerShell? That's a tough question
I'm a big fan of both. Because of the power of the
notebook, they're just so easy to use. Even the Azure Cloud Shell
has both of these things pre-installed. So I really figure out what I'm trying
to do and then I try to see which one is easier to use. I would say
the Azure CLI maybe is a little less of both. Azure PowerShell has just a few
things. For example, invoking a failover, you can only do in Azure PowerShell. You can't do it in
Azure CLI. So I wouldn't say I have a favorite. I would say my favorite is just using
PowerShell and then these are just two different ways to do that
But maybe I tend to use, I don't know, it's hard to say. I use both
Anytime in the store, I use Azure CLI. If I'm doing a failover
I use Azure PowerShell. I don't really have a lot of reasons
You're doing stuff randomly, right? I think I think it's taking more than one hour
You both go ahead and wrap. Let me ask you a question that is not
related to this topic. Apart from this, you're a manager, you're a site scientist
my goodness, what do you do to keep yourself entertained with other
mental hobbies? No, sure. I would say my biggest quarantine hobby, which is because I have a few new
quarantine hobbies, my biggest one has become my dog, which I think
is so important in this time where I'm inside and probably everyone here is inside all the time
This dog gives me a reason to go outside. Get off the computer for a few minutes
In this time, we're just always connected and also it helps because we have a
local park and everyone's outside and it's safe and you can social distance
and you bring your dog there and it gives you a way to have some social interaction
in a safe way. I think that's been the other big one. Maybe the other
one is I've gotten into the whole bread-making scheme that everyone's making bread so I have
my staff and I make bread like once a week. You need to explain. You need to explain
that this is both the bread and all. Exactly. Finding ways to keep yourself
entertained, keep yourself stimulated, connect with other people. I love to do things like
this, especially discussions because you have them so engaging. It makes it a lot more fun
and it makes being at home, oftentimes by yourself, a better. I think the
community is really a big part of that. That's great. It was such an amazing session
and we covered everything and I think everyone would go ahead and get an idea
of the practices. You have these demos. You have these amazing slides and I think you'll get
a bunch of resources. Definitely, anyone who's watching us, go ahead and check out
our data expose show that's also very interesting. Definitely go ahead and check that out and I
think in the next episode of our community we have almost 10 minutes
which is long. I think we can even talk about the other sessions and maybe
that would be interesting too. With that, Anciana, thank you so much
for tuning in today. Thank you for joining us very early in the morning. We would love
to have you back. You are a true community leader. Thank you so much for your time
and have a nice day. Thank you. Bye. Take care