Toad World® Forums

Feature Request: Less steps to restore a database


#1

One of the things I do most frequently in Toad is to restore a database from a
file so I can work on it on my dev machine.

It takes WAY too many steps to do this in Toad.

Step 1: Choose Restore Database

Step 2: Change the “From Database” default from True to false

Step 3: Click the Builder Button to the right of the “Device” option

Step 4: (Assuming Backup Media says “File”, which it currently does
default to) click “Add”

Step 5: Browse to, and select the file, then click OK

Step 6: Click OK

Step 7: In the “To Database” field type the name of the database you
want to mount it as

Step 8: Click the checkbox in the “Restore” column at the bottom of
the screen beside the name of the backup file you just added.

Step 9: Click Options

Step 10: Click in the Restore As box, and replace the invalid path that was the
path where the file was stored on the source server, and replace it a path that
actually exists on your machine – say for example the path you browsed to
to select the file in the first place!

Step 10: Click “Yes” to update the other file with that path.

Step 11: Click OK

THIS IS WAY TOO MANY STEPS.

What I want, is a “Quick restore file from .bak file” option added
to Toad’s restore dialog.

In that mode, the steps would be as follows:

Step 1: Choose Restore Database

Step 2: Browse to the .bak file you want to restore.

Step 3: Answer “Yes” to a new prompt: “Use file path as
restore path?”

Step 4: Optionally change the To database name from the default you will have
pulled from the filename to something else – probably by just deleting off
the extra stuff you don’t need at the end.

Step 5: Click OK

Now that’s a nice, streamlined procedure.

Please consider it. I must spend at least 15 minutes a day just wasting time
clicking through the existing steps.

I’m not trying to suggest my streamlined procedure would work for
everyone, it probably wouldn’t, but when you’ve got a .bak file that
contains a full backup, it would work and would save tons of time.

Darren


#2

Hi Darren,
thank you for the input. It seems to me that we didn’t think about Restore operation in this way. What you say is reasonable. We will try to implement some easy-way-to-restore like you suggested.
I’ve created ST80001 to track your request (wow, look at the number :).

regards,
Alexander


#3

Hey Darren and Alex, I kind-of-Sort-of agree with this being a nuisance.

I have a stored proc I wrote to accomplish the backup and restore fast, let me
dig it up and post it … It performed the backup and restore and logged the
activity performed by the Stored Procedure into an activity table… I just have
to dig it up. Who know it could be the basis of this CR !!!

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678-414-0090 my cell Primary
image001.gif


#4

Hey Darren and Alex, I kind-of-Sort-of agree with this being a nuisance.

I have a stored proc I wrote to accomplish the backup and restore fast, let me
dig it up and post it … It performed the backup and restore and logged the
activity performed by the Stored Procedure into an activity table… I just have
to dig it up. Who know it could be the basis of this CR !!!

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678-414-0090 my cell Primary
image002.jpeg