Skip to content

Latest commit

 

History

History
90 lines (68 loc) · 5.63 KB

sys-dm-operation-status-azure-sql-database.md

File metadata and controls

90 lines (68 loc) · 5.63 KB
title description author ms.author ms.reviewer ms.date ms.service ms.topic f1_keywords helpviewer_keywords dev_langs monikerRange
sys.dm_operation_status
sys.dm_operation_status
rwestMSFT
randolphwest
wiassaf
02/13/2023
azure-sql-database
reference
dm_operation_status_TSQL
dm_operation_status
sys.dm_operation_status
sys.dm_operation_status_TSQL
dm_operation_status dynamic management view
sys.dm_operation_status dynamic management view
TSQL
=azuresqldb-current||=azure-sqldw-latest||=azuresqldb-mi-current

sys.dm_operation_status

[!INCLUDE asdb-asdbmi-asa]

Returns information about operations performed on databases in a [!INCLUDE ssazure-sqldb] server.

Column name Data type Description
session_activity_id uniqueidentifier ID of the operation. Not null.
resource_type int Denotes the type of resource on which the operation is performed. Not null. In the current release, this view tracks operations performed on [!INCLUDEssSDS] only, and the corresponding integer value is 0.
resource_type_desc nvarchar(2048) Description of the resource type on which the operation is performed. In the current release, this view tracks operations performed on [!INCLUDEssSDS] only.
major_resource_id sql_variant Name of the [!INCLUDEssSDS] on which the operation is performed. Not null.
minor_resource_id sql_variant For internal use only. Not null.
operation nvarchar(60) Operation performed on a [!INCLUDEssSDS], such as CREATE or ALTER.
state tinyint The state of the operation.

0 = Pending
1 = In progress
2 = Completed
3 = Failed
4 = Cancel in progress
5 = Cancelled
state_desc nvarchar(120) PENDING = operation is waiting for resource or quota availability.

IN_PROGRESS = operation has started and is in progress.

COMPLETED = operation completed successfully.

FAILED = operation failed. See the error_desc column for details.

CANCEL_IN_PROGRESS = operation is in the process of being cancelled.

CANCELLED = operation stopped at the request of the user.
percent_complete int Percentage of operation that has completed. Valid values are listed below. Not null.

0 = Operation not started

50 = Operation in progress. For restore operations, this will be a value between 1 to 99, indicating how far along the operation is in percent.

100 = Operation complete
error_code int Code indicating the error that occurred during a failed operation. If the value is 0, it indicates that the operation completed successfully.
error_desc nvarchar(2048) Description of the error that occurred during a failed operation.
error_severity int Severity level of the error that occurred during a failed operation. For more information about error severities, see Database Engine Error Severities.
error_state int Reserved for future use. Future compatibility is not guaranteed.
start_time datetime Timestamp when the operation started.
last_modify_time datetime Timestamp when the record was last modified for a long running operation. When the operation has completed successfully, this field displays the timestamp when the operation completed.

Permissions

This view is only available in the master database to the server-level principal login.

Remarks

To use this view, you must be connected to the master database. Use the sys.dm_operation_status view in the master database of the [!INCLUDEssSDS] server to track the status of the following operations performed on a [!INCLUDEssSDS]:

  • Create database

  • Copy database. Database Copy creates a record in this view on both the source and target servers.

  • Alter database

  • Change the performance level of a service tier

  • Change the service tier of a database, such as changing from Basic to Standard.

  • Setting up a Geo-Replication relationship

  • Terminating a Geo-Replication relationship

  • Restore database

  • Delete database

The information in this view is retained for approximately 1 hour. You can use the Azure Activity Log to view details of operations in the last 90 days. For retention more than 90 days, consider sending Activity Log entries to a Log Analytics workspace.

Example

Show most recent geo-replication operations associated with database mydb:

SELECT *
FROM sys.dm_operation_status
WHERE major_resource_id = 'mydb'
ORDER BY start_time DESC;

Next steps