The following table lists and describes existing migration job statuses:
| Migration job status | Description | Possible substatus | Possible user actions |
|---|---|---|---|
| Not started | The migration job is ready but still not running. This status is relevant if the migration job was created but wasn't started. | None | Start. Delete. |
| Starting... | The migration job is in the process of being started. This is an intermediate status that occurs when a migration job is
started. Starting the migration job takes between a few seconds and a few
minutes. The status changes to Running. |
None | Delete. |
| Running | The migration job is actively running. | ||
| Running with errors | This status means that Database Migration Service encountered errors with
your migration. Faulty operations will be retried,
and errors clear automatically once the underlying issue is resolved.
Database Migration Service continues migrating data unaffected by the error. |
Incremental load. | Stop. Restart. Promote. |
| Completed | None | Delete. | |
| Failed | The migration job failed because of an error. You need to restart the migration job after the issue is fixed. | ||
| Restarting | The migration job is in the process of being restarted. | None | Delete. |
| Stopped | The migration job is stopped. | The last status before the migration job has stopped. | |
| Resuming | The migration job is in the process of being resumed. | None | Delete. |
| Stopping... | The migration job is in the process of stopping after Stop was
invoked. This is an intermediate status that occurs when a user stops a
migration job. Stopping the job takes around a
minute, during which the status is Stopping. Subsequently, the status
changes to Stopped. |
None | Delete |
| Ready to promote | Database Migration Service stops continuous load when it detects a transaction
log file whose name ends in the .finalThis status doesn't occur if you just stop uploading transaction
log backup files instead of using a file with the
|
None | Promote |