>> Hello, everyone. My name is Colin Murphy,
Product Marketing Manager in Microsoft.
I am joined today with Raj.
Raj will you introduce yourself for me?
>> Sure. My name is Raj Pochiraju,
I'm the Principal Engineering Architect
in the Azure data engineering.
My primary focus is to enable
seamless migration experience to
Azure databases using the tools and services that our team build.
>> So what's important about all these tools and services?
>> Yeah, like I said, these tools and
services will really help customers
to have a seamless
and lift and shift to migration experience to Azure.
So before I really go to introduce those tools and services,
let me step back a little bit and talk
about why these tools and services are that important,
and what are the specific trends that
we're seeing in the Cloud migrations.
As you see in this slide,
by 2020 it is estimated that
90 percent of the organizations will use either IaaS,
the Infrastructure as a Service,
or Platform as a Service and 80 percent of
the enterprise workloads will be in the Cloud by 2020,
so this really brings a lot of
demand for the Cloud migrations and we want to make sure
that we provide the necessary tools and
services that help customers to take this migration journey.
>> Is this specifically aimed at
database migrations or is it just all up migrating to the Cloud?
>> Yes. So my team or the tools and services
that our team build is primarily
focuses on the database migrations.
But we also have a end-to-end migration story,
that enables the migrations across
the servers, databases, and applications.
Before we go to
the migration strategies and
as well as the various migration phases,
let me talk a little bit about what are the factors
that really driving these Cloud migrations.
I'm not going to specifically talk about all of them but
at least I want to mention couple of them here,
that we are really seeing a lot.
One of them is Data Center Contract Expiration,
a lot of these customers are running out of
their data center releases and this is
the time that they really want to migrate to the Cloud,
so that they can really do
the cost savings and all that and then also they can bring a lot
of efficiencies into their applications
or by using the native Cloud advancements.
>> Otherwise, they've got to commit to a two-year lease
of data center again or something?
>> That's correct.
>> A big spend.
>> Yeah. The other driving factor is we're
seeing the handoff support for the software,
especially for SQL Server 2008,
2008 R2 and Windows 2008 and Windows 2008 R2.
This combination is running out of support pretty soon,
so customers really want to think
about modernizing their applications,
migrating them to the Cloud so that they don't have to
deal with any of these end of support stories anymore.
>> So what are some of the ways they can move,
they can mitigate that in this whole?
>> So basically, I don't have the slide for that
but the ways that they can
mitigate the end of support
is first thing is they can migrate to the Cloud,
which is modernized into the Cloud,
so that they can comply with
the Microsoft support services and all that stuffs or they can
stay On-Premises but they can also upgrade to
the latest versions or they
can do a lifting shift migration as it is to the Azure,
specifically to the Azure VMs and then they
can get a three-year self extended warranty for free.
Or in the worst-case scenario,
if you still want to stay On Prem and do not want to upgrade
then you might end up with buying the extended warranty.
Those are the various options that the customers have today.
>> So they've got plenty of options.
>> Plenty of options, yes and we're more than happy to work with
customers to enable
the specific option that really works for them.
>> Okay. Right.
>> So in terms of modernizing to the Cloud in
our various strategies that we are seeing customers adapting,
there are four different strategies that we see are
widely adopted and the very first one is that
rehost essentially means lift
and shifting your environment as it is to the Cloud.
Typically, if you're looking at
the applications you can migrate your applications
as it is to the virtual machines running on the Azure,
at the same time when it comes to the databases specifically for
SQL Server you can migrate to Azure SQL Database Managed Instance,
which is a Platform as a Service and mainly
used for providing close to 100 percent compatibility with
your On-Premises instance model and also
provide you a lift and shift migration experience to you
so that you don't have to make changes to
your existing environment and existing applications.
But you can still migrate to PaaS
and then get all the benefits of the PaaS.
The other strategy is that we are seeing the refactor,
where that is the first time that you are
trying to modernize your applications,
the very first step in modernizing your applications,
where you are trying to containerize
your applications and migrating
your databases to Platform as a Service.
We expect little code changes for that factor,
we don't really expect any significant application changes.
Rearchitect is another strategy customer is
adopting where they're going to be modularizing
their applications to small modules
for better scalability and better high availability,
when they migrate to the Cloud.
>> That can use micro services and things like that.
>> That might require significant chord
changes into your existing applications.
Then the final one is the rebuild where a completely rebuilding
the entire applications from the scratch by
leveraging all the native Cloud services,
which requires a significant effort actually.
>> For our new project.
>> Correct. What we are seeing that
most of the customers are adapting rehost and refactor,
majority of the customers that they're
using these strategies to migrate to the Cloud.
>> Earlier on you mentioned the rehosting,
you mentioned managed instance,
so how would a customer figure out whether they need to go to
that one or the single version of Azure SQL Database?
>> Sounds good, makes sense.
My next slide really helps you along those lines.
As we understand the migration strategies
the next step is what it really takes to migrate,
whether you adapt a lift and shift migration or whether you adapt
a refactor and how that journey is going to look like.
That will address what specific tools
that will help them to find out whether
SQL DB or SQL managed instance which platform that is good,
fit for the customer and all that stuff.
So if you look at the various phases in the migration journey,
you see assessment phase is the first phase
where you will go and then discover all your environment,
find out all the application dependencies,
which of these databases needs to be migrated together,
what would be the platform,
is good fit for me,
for my workload, that I can be able to
migrate with less effort and also what
would be the size of my target when I migrate
to and what are the migration blockers that I need to address,
what specific things that I need to
fix after the migration is done.
All that analysis happens during
the assessment phase and then essentially
it gives you-all the planning that is required
for making a successful migration journey.
>> Then we got tools and
documentation and everything to
help people out with that phase to phase?
>> Exactly, yeah. Then the next stage is the migrate phase where
you would decide based
on the inputs that you get from the assessment,
the recommendations you get from the assessment,
you would want to decide your workloads that
are good fit for lift and shift or whether it is good fit
for a refactor or those strategies
that you would decide and you also find out
the specific tools that you're going
to use to do the migrations and assessments.
Then you essentially migrate your schema,
migrate your databases and then also migrate
any other artifacts that your applications are dependent on.
The third stage is an optimize once you get to Cloud,
the journey actually starts right there in my opinion,
because that's where you're going to start leveraging
all the native Cloud services to see if you can further
optimize your TCO or maybe you can
bring much more efficiencies to your customer experiences,
get more business insights so that you can
really use for the complete advantage,
all those innovations happens once you migrate to the Cloud.
>> So that they can take advantage of things like the auto tuning
or performance tuning where it
gives you recommendations to optimize, yes.
>> Correct. Then they get much more richer business insights
with all the native Cloud analytical services,
so that they can use for the compute advantage and other staff.
>> It's a great way to modernize.
>> Yeah. Then the last stage is the secure and manage,
security is something that you don't want
to just look at at the end of the migration journey,
something that you would want to look at
the whole migration lifecycle,
but the security that I'm talking particularly here about,
there are rich services out there in Azure,
really help secure your existing environment,
so you might want to start leveraging those services.
The same thing with the manage like we have
rich capabilities to monitor your applications,
to monitor your infrastructure,
to monitor your PaaS services,
so you would want to leverage those things as well.
Now, given that I have these different phases now let me
introduce you with a specific tools and services
that we built that help you to take this journey.
On the left side we have all the sources and on
the right side we have all the targets that we support.
If you look at on the left side we support migrating from
SQL Server 2005 all the way up to 2017,
that you can migrate to SQL DB,
SQL Managed Instance or SQL VM.
Same thing with the heterogeneous sources
like Oracle, Sybase, DB2 that you can migrate to Cloud,
we have support for migrations from open-source,
databases like MySQL and Postgres that you can migrate to
the Platform as a Service aspects of
the Azure, PostgreSQL and MySQL.
NoSQL space you can migrate from Cassandra
and MongoDB to Cosmos DB.
Not only that we support migrating from On Prem,
we also support migrating from AWS
and Google Cloud as well.
The specific tools that you can use for the assessment,
now let's map these tools with
the migration generally that we talked about.
For the assessments you can use
Azure migrate service that you can use to discover,
find out all the app dependencies and then find out the TC,
and all the stuff that you can use Azure migrate service.
DMA, Data Migration Assistant Tool that really
helps you to assess your On-Premises databases,
you have to really find out what it
really takes to migrate them to the Cloud.
>> This is a free tool.
>> This is a free tool, publicly
downloadable and it is an On-Premises tool.
>> All right.
>> Then you can also find out the specific target
that you want to migrate, you asked that question, right?
Whether I do migrate to MI,
whether do I migrate to SQL DB VM,
this too really help you to find out what
is target which could fit for you.
>> That's great. So just download a free tool,
that sort of parameters?
>> Yeah.
>> Point to my source and wallah.
>> Yeah, sounds good. Then we also have the SSMA,
SQL Server Migration Assistant tool that really
helps customers to assess their other sources
of databases like Oracle, Sybase,
DB2, but also help you to do the schema conversions,
which is critical stage in
migrating from heterogeneous sources to Azure.
Then we also have a tool called the DEA,
Database Experimentation Assistant Tool,
that really helps you to validate
your target workload ahead of your migration,
so that you can really understand how your target is going to
respond to your business applications
so that you have a confidence.
>> It's really important, I don't
want to move to the Cloud and find out these.
>> Without knowing anything, right?
>> Yeah.
>> Then there's Azure Database Migration Service,
a service which is fully
managed service on the Azure which really gives you
a seamless migration experience
to Azure databases with minimal downtime,
with zero downtime migration experience.
It also provides a resilient migration experience for
all the implemented features that you might
encounter and also more importantly,
it has a richer orchestration capabilities,
that you can really group together all those databases
into a single project and then do the migrations.
>> All right. So I can move my application, the database with a.
>> With a single migration project as a group.
>> As a group, wow that's really cool.
>> Remember that everything that I just shared,
you can also use rest
APIs that we provide so that you can completely
automate these migrations to scale across
your data center as one.
>> So if I got hundreds of databases,
I can just use these tools instead of
just script and automate to moving all of them?
>> Yeah.
>> Perfect.
>> So I have plenty of the documentation here,
there are some links that I provided that you can understand.
Probably in my next video,
I can give some cool demo,
so you can use my tools to do these migrations.
>> Okay, great. Thank you very much Raj and
I hope that was useful for everyone and
we will see you next time. Thank you.
>> Thank you.
[MUSIC]