Canceling Single to Flex server Migration Drops Data From Target Server which contradicts docs about azure-docs HOT 5 OPEN

@atmask
Thanks for your feedback! We will investigate and update as appropriate.

from azure-docs.

Hello @atmask
To clarify, canceling a migration initiated from the Azure Database Migration Service (DMS) should not result in the removal of data from the target server. However, if you cancel a migration that was initiated using a different method, such as the Single to Flex Migration tool, the behavior may be different.

If you canceled your migration using the Single to Flex Migration tool and the data was removed from the target server, it is possible that this is the expected behavior for that tool. I would recommend reviewing the documentation for the specific tool you used to initiate the migration to see if there is any information about the behavior of canceling a migration.

I hope this helps clarify the situation. If there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

from azure-docs.

@Naveenommi-MSFT sure, that’s fine that the single to flex tool has different behaviour than classic DMS, however, the docs linked above are specific to the single to flex migration tool. The steps in the instructions for initiating the dms use the single to flex migration tool. The behaviours listed in the above docs should be consistent with that tool and not classic DMS so it would still be good to update them and make apparent the behaviour around cancelling DMS

from azure-docs.

@atmask
Thank you for bringing this to our attention.
I've delegated this to content author @hariramt, who will review it and offer their insightful opinions.

from azure-docs.

Hi @atmask , @Naveenommi-MSFT ,

Thanks for bringing it to my attention. This has been fixed and the udpate should reflect within the next 24 hours.

from azure-docs.