[MUSIC].
>> Hi. I'm Anna Thomas,
and I'm a Data and Applied Scientist on
the Azure Data Team working on
SQL and I'm joined today by my colleague.
>> I'm Jeroen ter Heerdt,
and I'm a Program Manager in the Azure Data Team too.
>> We're excited to have you all today.
Today, Jeroen is going to talk to
us a little bit about Hyperscale.
What are you going to go through today?
>> Well, Hyperscale is a new service
here for Azure SQL that we just introduced in May.
Today, I'm going to show how to migrate
a database from Azure SQL like regular Azure SQL to Hyperscale.
>> Cool, awesome. So what do you got there?
>> So the way this works,
I am in the Azure Portal here,
let me zoom in a little bit.
So I'm in the Azure Portal,
I have a standard SQL database here.
Very simple one, is general purpose pricing tier, nothing special.
I'll take this database and migrate it to Hyperscale.
So in order to do that,
what I do is I click here,
I go to "Configure", and on "Configure",
I can see that my database is currently in general purpose
and I can change that by
going to Hyperscale over here on the right,
and then I can make some configuration changes.
I can choose, for example,
the amount of vCores that I want or the amount
of read-only replicas that I need.
So yeah, that's basically the formula I get.
>> Jeroen, what is that little warning sign we're getting?
>> Yeah, that's a good one. Good catch.
The warning sign is actually about
notifying you that this is a one-way street you're entering.
So there's no way once you
migrated your standard database to Hyperscale,
there's no way to go back at this moment.
So this is brand new,
this might change in the future, but for now,
there's notices here to tell you be warned,
you can't go back after you went to Hyperscale.
>> So when I'm testing and stuff,
should I use a copy?
>> Yeah, I would definitely just take a copy.
It's very easy to take a copy of any database in Azure.
So once you have it, click copy
and migrate to Hyperscale on the copy.
Then once you're happy with how everything works,
you can then change the connection string in
your application to point to this new Hyperscale version.
>> Awesome. Cool. Thanks.
>> So what I'll do is I'll click here on I understand
to let the portal know that I read
the notice and I understand what
the issue is or what I'm getting myself into.
Then I'll have to choose the compute generations,
I'll always go with the latest Gen5,
and I can change the vCores to virtual cores,
the amount of replicas that I want,
and I'll click "Apply".
Then what will happen is that the database is
now migrating to Hyperscale.
>> That's it.
>> That's it. So easy.
>> Oh, wow. So what types of use cases would I want
to- why would I want to move to
Hyperscale while we're letting it switch over?
>> Sure. Well, the biggest reason is actually scale,
so either scale in terms of
storage or scale in terms of query performance.
So Azure SQL itself
has approximately four terabyte file size limit.
If you have a database larger than that, what do you do?
Well, Hyperscale is your answer.
So if you have let's say, I don't know,
40 terabyte database, or 40 terabyte data warehouse,
or 40 terabyte whatever database,
hyperscale can then host that database for you.
Then with the read-only replicas,
you get even more query performance over all of that mass of data.
So those are the two main reasons due to migrate to Hyperscale.
>> Is there a certain number of read-only
replicas that I get with Hyperscale or can I configure it?
>> You can configure it, it's
between zero to four, so you can choose.
I think by default it goes to one,
but you can dial it back to zero if you don't
want any read-only replicas,
you can change it later as well,
you can up the vCores,
you can change or lower the number of replicas.
So those two settings you can change after deployment.
>> Awesome. Cool. So hopefully,
that was useful for you all.
Thanks for joining us today,
and if you're interested in
Hyperscale feel free to leave us a like,
subscribe to our channel,
even leave us a comment on what you're most
excited about Hyperscale and tune in next time. Thank you.
[MUSIC]