[MUSIC]
Hello, my name is Lindsey Allen.
I'm one of the Group Program Manager at Microsoft Database Systems.
>> Hi, I'm Murat Ozturan, I'm the Group Program Manager for
Data Migrations.
>> So in this video, next ten minutes or so, we're gonna
talk about Azure SQL Database and the migration to Azure SQL Database.
>> Mm-hm.
>> So Azure SQL Database is the only public cloud that it is a service.
Thus, can learn and adapt based on your unique patterns of your
applications and can scale on the fly without a downtime,
and can support you to build multi-tenancy application at ease.
And had a build in security intelligence to help protect
your data, and does work very well with your environment as well,
with your on-prem and wherever your application deploys to.
>> Yes, and this is very exciting for a new application, but
also you can migrate and
upgrade your existing SQL Servers to Azure SQL Database.
>> Yeah, so you can actually deploy your application against
the SQL Database on premise, and we have tools, you're gonna show us,
to move your database.
>> I'll be showing the tools for you.
And one of the things when you're moving the upgrades and
migrations is the methodology that goes with it.
>> Sure.
>> So it's very important that you define and plan and
change the necessary things and remediate.
Then migrate, test the system, then finally deploy it.
>> Ah-ha.
>> And we do have tools for
it that you can easily download from the Internet.
And I'll show you how to do this very easily.
>> And the tools is built with a real world process of a migrating
application.
A redeployed application in mine is end to end.
>> Yes, it's an end to end tool that moves your data from existing SQL
servers to Azure Database or a newer version of SQL Server.
>> Great, can't wait to see it.
>> Here's the demo.
So, let's look at this, this is Data Migration Assistant.
Let me launch it, and, Get the full screen up there.
And let me create first a new project for assessment.
So let's call this thing DataAmpAssessment and
we create an Azure SQL Database from SQL Server.
And we go in there, and run for check databases in there.
So Server name, we put it as a SQL 2008 server that we have,
that we are gonna migrate to SQL 2016.
You connect to the server, and
you get an inventory database that you can.
You add that server, then you start seeing the databases in it.
So assessment goes into place and they start running with it.
It goes through all the different checks.
So what happens is, you see the Windows authenticator is
not supported, unsupported features from one version to another.
As you would imagine,
you may have also some compatibility issues with compact levels.
So you have a very detailed information for
each one of the errors that you get in there.
For example, Compatibility 100, you got Migration blockers,
Behavior changes and Deprecated features.
So let's look at the DBCC command that is been replicated and
no longer works the way it was in the previous version.
So you do only not see the details, what's the impact of this
feature in there, but you actually see the procedures that is involved.
Old way to do it, line and column level, so
it's very easy to identify and for you to go in there and change it.
And different things, for example you can look at unqualified joins.
It's a new way, new behavior, so it gives you the details how to do it.
Then it again, gives you line and column numbers,
so for you to easily to identifying them.
Deprecated data types, for example text, image and intakes,
what do you need to do, and what's the impact to it?
So you can export it as a JSON or CSV file to be able to hand it over
all this information to your developers for it to be changed.
Then let's go and actually do the migration.
So for migration you create another project, and you choose SQL server.
Let's say DataAmpMigrations, target server you identify as a SQL server.
And you connect to your both servers.
First, SQL 2008 R2, then SQL 2016,
which is your target machine.
Then you go Next, And
it basically tells you whether it's gonna take it back up.
So you need to find a shared that both of them access,
both of the databases can access.
And you have an alternative fuel,
you may be able to want to change it.
Then you say these are the logins that I would like to migrate as
well from the object's perspective.
Then you say Start Migrations.
So what it does in the background, basically it changes.
And it goes and looks at all the server objects and
start migrating them.
It takes a backup from the previous version and
restores it in SQL 2016.
And this is how VA works and is a very simple user interface,
and it works very efficiently.
>> You showed us how to move my database from one place to another
to Azure SQL Database.
>> Yes.
>> So, how would I know my application still work well?
>> So we have a little tool for that as well.
It's called Data Experimentation System.
This is a A/B testing of two separate SQL Server instances that
you can replay your existing workloads, and see if it's working,
and is it performing better or worse than before?
>> Or actually still work well, right?
>> Yes, it will work well, and we'll show you how to do it.
So, what do you do?
Your existing environment, you capture the analytics in there.
Then you replay it in two separate environments.
One, the existing system, the other one is the new environment.
Then you put the data in an analytics environment,
then you get a report for it with charts and details.
Let me- >> So
it should actually tell you how the application,
the same workload performs, right?
>> Yes.
>> In each environment, that's awesome.
>> So, let me show you how that works.
So for Data Experimentation Assistant,
we launch the Data Experimentation.
Let me put it as a full screen.
So you can connect to existing environment, that's New Capture.
And you connect to your existing environment and start capturing.
And you decide how long you're gonna capture.
You would like choose sometime that the majority of
applications accesses to all different things.
Now, we choose 180 minutes, and
it's gonna have a shares that it's gonna capture.
Like any good cook place, you can replay it as well.
So you capture the traces that you can replay
in your two target machines.
Okay, like any good cook show, I have the analysis is already done.
We are not gonna wait three hours for it.
So let me connect to the SQL 2016.
That's made its analysis in there, and look at the report.
When you get in the end of the results you get the charts.
So this is the interface that you're gonna see.
The threshold SQL 2008 source, SQL 2016,
then you look at the degraded queries in there.
They are sorted out from top to bottom.
Most degraded queries out there and
you get all the information in there.
One of the reasons, probably in previous version, you optimized it
so much to that engine that you might have to change stuff.
So you get the matrix, you get the execution plans.
So you got all the details on that specific query, and
what is being put in there.
For both in target one and target one, and
be able to compare it and see what do you need to do
to get a better performance from the new system, and how to optimize it.
One of the other features that's important is errors.
So you didn't have certain errors before,
there's the new errors created.
So you look at it, what went wrong?
So you can look at the error information.
This specific query didn't work.
And if you look at their information you're gonna see that
there's a keyword next to the compute that that's not gonna work.
It's generated an error.
So you can go back and check, and
correct those errors before you deployed your system.
So it gives you more details on each query and each error information.
So you can go down even further and see each valid
object's different interfaces that's happening in target one and
target two, and be able to get the analysis in there.
So this is a very good user interface
to be able to do the actual A/B testing and
see the results in a very graphical and easy to understand methods.
>> So we just saw the demo on how to easily move your
application data from on-prem to Azure SQL database.
And also have this very nice tool to help you A/B test your application.
>> Yes, and those tools are free for you to download.
>> So I would like you to actually give it a try.
And there's a free trial of Azure SQL Databases.
And all of these, both of these tools, are available on Internet for
free download.
So just give it a try and you will like it.
>> Yes, Data Migration Assistant and Data Experimentation Assistant.
They're both for you to facilitate your migrations and
make your life easier.
>> Thank you.
[MUSIC]