>> Learn about some of the latest updates to
the migration extension in Azure Data Studio,
this week on Data Exposed.
[MUSIC]
Hi,
I'm Anna Hoffman and welcome to this episode of Data Exposed.
Today I'm joined by Carlos.
Carlos, thanks so much for coming on the show.
>> Hey, yeah, thanks for having me my first time into show.
So very excited about it.
>> Great to have you. Why don't you tell
us a little bit about yourself?
>> Sure. My name is Carlos Robles.
I am a senior product manager in
the Azure data modernization team.
This team is responsible of
building the different migration tools for
customers use to migrate
their on-premises database workloads into Azure.
>> Awesome. Cool. It's great to have you on the show.
Seems like you're the right person to be
talking about for the topic today,
which is migrating SQL Server to
Azure SQL offline with Azure Data Studio.
Now before we get into that,
I want to hear a little bit about
this migration extension in Azure Data Studio.
>> Just to talk a little bit of
the SQL migration extension for Azure Data Studio.
These extension provides our customer and simplified experience
to perform assessment so they
can understand their migration readiness.
They can also get Azure recommendations
to a data collection process we have in the tool.
Finally, they can migrate
whether they decide to do it offline or online,
to the different Azure SQL targets as Azure SQL MI,
SQL Server for Azure SQL VM,
and now introducing in preview
Azure SQL Database for offline migrations.
>> Got it, that's pretty cool. Why would someone
use Azure Data Studio for this?
>> That's a really great question.
There is many benefits of using Azure Data Studio.
As you can see here on the screen I have different listed.
The first one is that now we have an integrated experience.
In the past, we have different tools for the assessment.
But now in this new experience,
we have everything in a single place.
The next one is that it is easy to use and configure.
One of my favorite things about
Azure Data Studio is that is cross-platform.
Next one as you can see
the online and offline migration capability
for the different targets that I already mentioned.
>> Awesome. Cool. Now we're using
Azure Data Studio migration extension right here. What's new?
>> I have great news.
We recently released a couple of things.
The first one I mentioned in preview,
we now support Azure SQL Database as a target.
We also introduced a couple of new capabilities.
The first one you see here is that now we
allow our customers to export the assessments and
also the Azure recommendations if they want to share
those our reports with their teams offline,
so they can do it now.
The last one is about the elastic model.
The elastic model for the Azure commendations is new.
By default, we use something we call the baseline model.
Baseline model is rule,
base, is restrictive.
The new model, the elastic model,
hence the name, is very flexible.
It will look at the same performance data,
all the different dimensions: IO,
RAM, storage, IO latency.
But let's say there is one specific I mentioned that
does not meet the workloads need in 100 percent,
but it does at 96 percent.
That SQL is not going to be rule out
from the list and it's going to be recommended.
But it's up to our customers if they want to enable it or not.
There is a significant price reduction if they want
to use a different SQL. That's it.
>> Awesome. Cool. I know you also have something
planned to show us. Let's take a look.
>> Let's jump into the demo.
I already have my Azure Data Studio in
store and the Azure SQL migration extension as you can see.
My goal here is to migrate
these ProductsMicro database from this BM into Azure SQL Database.
One of the prerequisites for this migration scenario is
to have the database already
created in the target and as well the schema.
I already took care of that using
the SQL database projects and extension. It's done.
I have a table here that has information about products,
IDs, and photo.
It's empty on my target.
Now I'm going to jump into this dashboard from the source server,
and I'm going to click here "Migrate to
Azure SQL" and I'm going to start a new session.
This is going to start the migration workflow.
The first thing our customers has to do is to select a database.
In this case, my database is ProductsMicro, then the target.
In this case, I want to show the preview of Azure SQL database.
I'm going to select Azure SQL DB here.
Here you can see that there is this section
where we can collect information about the actual recommendations.
I already complete that part.
For example, now with these new capabilities I mentioned,
you can enable elastic recommendations from the options.
If we look at the reports from here,
I can download the reports.
That's a new capability we are introducing.
The databases has different service tiers here recommended.
As you can see, the first one is on Business critical 4 vCore.
The next one I have is a little bit different.
It's general purpose,
2 vCore and the last one,
general purpose 4 vCore.
There is a service tier difference here.
It makes sense I'm trying to migrate different databases.
In this example, this one
has a different IO latency requirements.
That's why we are recommended at different service tier.
That's all from the SQL recommendations.
Now getting back to the migration,
so I need to check the the assessment results.
From here, our customers can learn if there is
any thing they have to solve
before moving to the target date selected.
In my case, I did this on purpose.
Service broker is not supported in Azure SQL DB, but it's okay.
I can perform the migration here.
That's an option we are providing letting our customer
know there is something they need to
fix before migrating to account day.
It's up to them to decide how they want to handle it.
If I click on "Next" here,
next step is to select my target.
I'm going to quickly navigate to my target.
This guy is my Azure SQL Database that
is on these location East US.
I'm going to go to East US.
Now I'm going to navigate to my resource group.
In front here I have to connect
to my target using my username and password.
Really quick. This button right here,
will make sure connectivity happens between source and target.
Then here at the bottom is
just a simple mapping between source and target.
In my case the database name is the same,
so I'm going to click on "Next".
Right here the migration load is offline,
so I'm going to go with the default.
Now once again, I'm getting asked to
provide the credentials in this case is from my source.
I'm going to enter the credentials for my source.
In this section, in the middle section you
see that I have a list of tables.
These are the tables that are going to be my target.
There are no rows of these tables.
These tables are empty.
I'm going to select all.
Customers can have different databases here,
different tables so they can filter these down.
My case, I'm going to go with going forward everything.
I'm going to click on "Next" and
now on this part is very important
here is when I have to create
my Azure Database Migration Service or use an existing one.
For these example, I have one that is already created.
I already completed the process to configure
the integration runtime. I'm ready to go.
I'm going to click on "Next".
Here is a summary of a migration.
All the different things I selected during the migration wizard,
and then I simply start the migration and that's all I have to do.
>> Cool. That's kicked off.
That would seem like it was super easy to do,
walks you through all the steps.
Like you said before,
you're just doing it all from one tool.
I think it's a really powerful now,
once this completes, what does it look like?
>> Once the migration is done,
and in this case it's done already.
There is information we show in these dashboard right here.
You can see from the source,
how many rows were written to the target.
This is very important for auditing purposes.
We show all the information for
every single table that is part of the migration.
I guess that's all I have.
>> Awesome, cool. Well, Carlos,
thanks so much for coming on the show.
I learned a lot about the extension as well,
some of the new capabilities including
this offline migration to Azure SQL database.
If you'd like this episode,
go ahead and give it a like,
leave us a comment and let us know what you think.
In the description you'll find some links to learn more,
so be sure to check those out.
But really you just have to go get the extinction, right?
>> That's right.
>> Go ahead and get started and we hope to see you
next time on Data Exposed. [MUSIC]