Ter uma ferramenta de ETL que capture os dados facilmente de qualquer lugar, transforme e deixe eles no layout adequado para enviar para o destino, é a chave de sucesso em uma migração desse tipo. Poucas fazem isso bem, e não conheço outra que faça tão facilmente quanto o datahub da iDashboards. Não perca tempo fazendo scripts malucos e super complexos e correndo o risco de não dar certo em projetos complexos. Procure um ETL de verdade e garanta a satisfação dos seus stakeholders

Let's assume you are migrating MySql database from Azure to AWS. In this case, try the things below. Something will definitely work out. 1. Verify the AWS MySql instance is publicly accessible. 2. Allow security groups in AWS to allow inbound connections from Azure's IP range or VPN. 3. Ensure Azure's NSG allows outbound connections to AWS. 4. Setup VPN between AWS and azure to securely link to environment 5. Check user has appropriate permission for migrate operations 6. Check DNS, AWS Mysql instance is resolvable from Azure 7. Test with a direct client Verifying above can solve your problem. Best of luck !!

1 .Cloud storage You can setup a scheduled in cloud automation rule to run delete old db after 6 month example 2. Turn on Schedule backups. 3. Set up notification e-mails in software for using migration data emails will be sent to these recipients when the job is successful. On failure email to: emails will be sent to these recipients if any error is encountered during the backup job. 4.weblog details This is very useful when you run SQL backups on multiple servers. Instead of accessing each computer separately through remote access, you can see the backup history for every computer on a single weblog page.