SQL Server Database Administrators always get to hear the age old question: How much longer will that restore or backup take? We’ve always answered this question based on past experiences along with some educated “guestimations.”
SELECT r.session_id ,r.command,CONVERT(NUMERIC(6,2),r.percent_complete)AS[Percent Complete],CONVERT(VARCHAR(20),DATEADD(ms,r.estimated_completion_time,GetDate()),20)AS[ETA Completion Time],CONVERT(NUMERIC(10,2),r.total_elapsed_time/1000.0/60.0)AS[Elapsed Min],CONVERT(NUMERIC(10,2),r.estimated_completion_time/1000.0/60.0)AS[ETA Min],CONVERT(NUMERIC(10,2),r.estimated_completion_time/1000.0/60.0/60.0)AS[ETA Hours]
,CASE WHEN r.statement_end_offset =-1 THEN 1000 ELSE (r.statement_end_offset-r.statement_start_offset)/2 END)
FROM sys.dm_exec_sql_text(sql_handle)))FROM sys.dm_exec_requests r
WHERE command IN(‘RESTORE DATABASE’,’BACKUP DATABASE’)
Subscribe to Our Blog
Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.
Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.
Imagine over 100 logins on the source server, you need to migrate them to the destination server. Wouldn’t it be awesome if we could automate the process?