Track SQL DB restore progress
Tracking in detail the restore of a SQL DB is mandatory in order to provide a transparent customer support. At this moment, one can only see if a restore is running (1%) or finished, but the restore progress in percentages cannot be seen. The only reply I can give at this moment to my customers about when the database restore will be finished, is somewhere within 24h.
Jacek Furmankiewicz commented
We are dealing with an emergency restore right now and everyone is stressed out not knowing how much we have left
Shane Seibert commented
I'm with Karl et al, any kind of progress indicator to help us make an estimate, track progress. The business counts on us and all we can tell them is "I started a restore and it appears to still be running." Of course, we are doing a restore, and we are probably all needing something out of it and being blind to its progression is a substantial detriment.
Dennis Riemersma commented
When restoring a database to a point in time, I would like to see it's progress, or at least some indicator showing that a restore is in progress.
It's 2019...even in the 1900's you could see the progress of a restore with a flat file database. Even a dmv would be nice. The number one question is "how long will it take before I can use the restored copy". I'll forward this "under review" response next time I'm asked by management to put a DB in Azure. During a duress situation, that question gets asked every 5 minutes...and of course it is my fault that I can't give a real answer.
Karl Burgdorf commented
Count me in on wanting this feature. Please, with a cherry on top!
Even medium sized databases I'm working with (60GB) can take a long time to restore. I don't mind how long it takes, I just need a rough ETA so I know when to come back to get it, and of course to know the job is still running ok.
Simon Litchfield commented
This is "RESTORE DATABASE". If we're using it, chances are we want to know it's working. If I leave the screen I don't even know if it's still running let alone progress.
This is a very basic feature and it should be implemented from the get go.
I think this feature is required when the restored db is very large.