marrowyung
asked on
MS tools to migration MS SQL to SQL Azure.
hi,
when migrating from MS SQL to SQL Azure, what the different between the MS tools: DMS and DMA,
please let me know.
when migrating from MS SQL to SQL Azure, what the different between the MS tools: DMS and DMA,
please let me know.
For MySQL i think your 1st stop should be :https://www.microsoft.com/en-us/download/details.aspx?id=54257
For Sybase similarly SSMA for SAP: https://www.microsoft.com/en-us/download/details.aspx?id=54256
ASKER
For Sybase similarly SSMA for SAP: https://www.microsoft.com/en-us/download/details.aspx?id=54256so by using this, Sybase logic and code still can't be migrate to SQL Azure? how about SQL Azurre manged instance?
ASKER
what the different between the MS tools: DMS and DMA
any idea?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
SQL Server migration documentation
this link is good ! but I don't see the difference between DMA and DMS !
or you point it out .
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
arnold ,
usually what I reached is, from SQL to SQL Azure, DMA and DMS is going to used but for compehensive solution will be offered by DMS.
For simply use, DMA can be consider first as someone did this before use DMA instead of DMS.
DMS is MS do it for us and DMA is we do it by ourselves ?
for an MS SQL to an MS SQL, you need the DMA to evaluate whether the MS SQL you are migrating from is compatible with the MS SQL you are migrating to.
usually what I reached is, from SQL to SQL Azure, DMA and DMS is going to used but for compehensive solution will be offered by DMS.
For simply use, DMA can be consider first as someone did this before use DMA instead of DMS.
The ADMS deals with a situation where you have to migrate a large number of Databases and data.oh that one is called ADMS and not DMS ? and it cost .......
It has a higher end service and thus cost.
DMS is MS do it for us and DMA is we do it by ourselves ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
There is no DMS, it is Azure Data Migration serviceoh, must launch from Azure portal ?
or must contact MS for DMS ....
?
so how about Sybase, Oracle, MySQL and DB2 migration? must use SSMA for it and do you know they can migrate ALL DB logic: function, sequence and SP to SQL Azure.
You use the tools, options based on where
Your question seems as though you have not defined your requirements.
The idea is to migrate the data, not to establish a one for one transition from what you gave now to sonething else.
Look at what DMA tells you.
SPs, and functions are part of the DB stracture.
Your question seems as though you have not defined your requirements.
The idea is to migrate the data, not to establish a one for one transition from what you gave now to sonething else.
Look at what DMA tells you.
SPs, and functions are part of the DB stracture.
ASKER
SPs, and functions are part of the DB stracture.
of course! this is what a lot of free tools can't migrate, and we can only consider paid tools
! which I have tried.
Your question seems as though you have not defined your requirements.
actually for this kind of migration project will have define of migrate all objects to the target one.
ASKER
ok, one thing, how about SSIS to ADF and SSAS to SQL AZure ? also DMA ?
can fully migrate all SSIS objects in SSIS to ADF ?
and I expect once migrate will fully take advantage of ADF?
can fully migrate all SSIS objects in SSIS to ADF ?
and I expect once migrate will fully take advantage of ADF?
What is your target setup?
Full core server running SQL server
Or you are running Linux with SQL server 2017??
Full core server running SQL server
Or you are running Linux with SQL server 2017??
ASKER
Full core server running SQL server
yes!
Or you are running Linux with SQL server 2017??SQL server on Windows.
What are the consideration for moving to the cloud versus using your existing setup.
Are all your applications will be moved into the azure platform, are you moving just the DB and a limited set.
SSRS! SSAS might be still on the insude connecting to the Azure via a VPN
you would either have to use local command line tools, powershell or use ssms remotely.
Are all your applications will be moved into the azure platform, are you moving just the DB and a limited set.
SSRS! SSAS might be still on the insude connecting to the Azure via a VPN
you would either have to use local command line tools, powershell or use ssms remotely.
ASKER
Are all your applications will be moved into the azure platform
expecting all of them , including middleware.
SSRS! SSAS might be still on the insude connecting to the Azure via a VPNkeep SSRS and SSIS and SSAS locallly ? and connect those component using VPN to the Azure ?
willl be very unstable then.
the concern is, will the application once move to the cloud will be slower and what should we do then ? this is the problem, DB I am sure not much problem at all ! but applicaiton ! usually should we rewrite all to fit the Azure ? any guideline on how to rebulit application?
Note, I explicitly limited which components can be out of azure, ssis is part and parcel to work where the DB is
Ssrs, SSAS could be on VPN, though only you know the frequency with which reports, or SSAS data is reviewed, used....
Before you move to azure, setup a lab using core server setup to familiarize yourself of the step to accomplish your common tasks.
Ssrs, SSAS could be on VPN, though only you know the frequency with which reports, or SSAS data is reviewed, used....
Before you move to azure, setup a lab using core server setup to familiarize yourself of the step to accomplish your common tasks.
ASKER
Before you move to azure, setup a lab using core server setup to familiarize yourself of the step to accomplish your common tasks.yeah, this is one of the way! and a very good way ! I did some migration project but none of them to the cloud DIRECTLY.
but one thing, is oracle ETL can upgrade/migrate to ADF ? any tools to use ?
"Ssrs, SSAS could be on VPN, though only you know the frequency with which reports, or SSAS data is reviewed, used....
"
so you mean no way to migration SSRS and SSAS to Azure ?
Ssrs, SSAS are SQL components and shoukd be available , issue/question resources and costs.
scope and breadth of your environment and needs. DB size,
Using oracle in an MS service might not be cost effective.
Do not know the answer to your question.
If your situation is complex, best to use the ADMS
scope and breadth of your environment and needs. DB size,
Using oracle in an MS service might not be cost effective.
Do not know the answer to your question.
If your situation is complex, best to use the ADMS
ASKER
Ssrs, SSAS are SQL components and should be available , issue/question resources and costs.really has to check..
"Using oracle in an MS service might not be cost effective."
nono, migration Oracle ETL to MS SQL ADF totally, so finally no more oracle ETL but ADF only.
"Do not know the answer to your question."
which one ?
"If your situation is complex, best to use the ADMS "
so ADMS supposed to be able to handle oracle ETL as well?
ASKER
when we run DMA, are we going to run it when the DB is in full loading so that DMA can tell us what SQL Azure tier we should buy ?
ASKER
reading this :
https://docs.microsoft.com/en-us/sql/dma/dma-overview?view=sql-server-ver15
"Assess on-premises SQL Server Integration Services (SSIS) package(s) migrating to Azure SQL Database or Azure SQL Database managed instance. The assessment helps to discover issues that can affect the migration. These are described as compatibility issues and are organized in the following categories:
DMA just assess it and try to find out problem, and that link do not say if it is to ADF, but it should be .. whatelse..
https://docs.microsoft.com/en-us/sql/dma/dma-overview?view=sql-server-ver15
"Assess on-premises SQL Server Integration Services (SSIS) package(s) migrating to Azure SQL Database or Azure SQL Database managed instance. The assessment helps to discover issues that can affect the migration. These are described as compatibility issues and are organized in the following categories:
- Migration blockers: discovers the compatibility issues that block migrating source package(s) to Azure. DMA provides recommendations to help you address those issues.
- Information issues: detects partially supported or deprecated features that are used in source package(s)."
DMA just assess it and try to find out problem, and that link do not say if it is to ADF, but it should be .. whatelse..
ASKER
tks both, might need to come back.