Move database

Moves the specified database from its current managed SQL Server instance to another server.

The MOVE_DATABASEjob may be skipped or rejected if the database is larger than 500 GB.

If a second MOVE_DATABASE job is submitted for the same database before the first job is complete, the first workflow job takes precedence. May return validation errors include attempting to move a database that was deleted before the job reaches the service, or conflicting delete-after-move scenarios as enforced by the server.

If successful, adds a MOVE_DATABASE job to the workflow queue and returns a 202 Accepted HTTP status code. The ID of the job is returned in the Location header of the response. Use the Get Admin Job operation to poll the status of the job.

🍐

Permissions

To perform this operation, a principal must belong to a user group that has been assigned the Data Admin role.

To learn more about role-based permissions, see Access Controls.

Headers
uuid
required

ID of resource group. Use the resource group associated with Data Admin (InitialResourceGroupForDATAADMIN); the operation consumes quota for nonmodeledConcurrentJobs. See Resource Groups.

Path Params
string
required

ID of database. Unique key of catalog entry,

Body Params
int64
required

ID of destination server (managed SQL Server instance) for the database.

Responses

Location header for status.

Language
Credentials
Header
URL
LoadingLoading…
Response
Choose an example:
application/json