Toad World® Forums

Feature Request: "Copy Path From File Selected"


#1

Something I do frequently is take a copy of a customer’s database and
mount it on a different machine. When I do that the path where I put the files
is where I want them mounted. But if the path is different from that of the
customer’s server I have to manually edit the “Currrent File
Path” fields.

When you open the attach database dialog, you click Add and browse to / select
the MDF file you want to mount.

The “top part” of the form now knows where the file is that you
selected.

What I want is a new button or prompt that allows the “Current File
Path” in the Database details section to use that path instead of the path
that’s stored in the file.

Call it what you want: “Set Current File Path from first file selected
above”, maybe a prompt after you select the file: “Use Path of File
Selected as Current File Path” Yes/No…

Maybe an option group:

“Get current file path from:”

“ o Paths stored in MDF File Selected”

“ o Path of file selected”

Whatever, just something that doesn’t require me to click in the Current
File Path box, highlight all the invalid path elements and then manually re-key
them with the actual file path. This is such a time waster and is so frustrating
because the computer already has all the information it needs to update the
path.

Thanks for considering this feature request.

Darren

image004.png
image001.png


#2

Darren !

We have all had this issue and your suggestion is a good one, but here again, I
believe the target should really be Microsoft and their assumptions on default
behavior.

Personally, I believe the current behavior is another good safe-guard and
resistance to change at MS is Like messing with Sasquatch on your request,
whether it be Microsoft (Sasquatch) or Quest.

If Quest wants to put this suggestion in play, then I am all for it, meaning I
support you on this idea. However, somebody should get Quest LiteSpeed for SQL
Server involved if such changes are truly going to be contemplated. I say this
because I see TOAD-SS as mimicking MS –SSMS and not really trying to make
a better wheel, that is being done in LiteSpeed.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn. com

678.414.0090 my cell Primary
image001.gif


#3

Darren !

We have all had this issue and your suggestion is a good one, but here again, I
believe the target should really be Microsoft and their assumptions on default
behavior.

Personally, I believe the current behavior is another good safe-guard and
resistance to change at MS is Like messing with Sasquatch on your request,
whether it be Microsoft (Sasquatch) or Quest.

If Quest wants to put this suggestion in play, then I am all for it, meaning I
support you on this idea. However, somebody should get Quest LiteSpeed for SQL
Server involved if such changes are truly going to be contemplated. I say this
because I see TOAD-SS as mimicking MS –SSMS and not really trying to make
a better wheel, that is being done in LiteSpeed.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn. com

678.414.0090 my cell Primary
image001.png


#4

Guys,

Out of 1000 database restores for me only 1 would be to the same server.
I’m a working at a software development company and every day I’m
restoring 2-3 different databases to test servers from production servers to
test updates, etc.

If you’re managing databases in your own network, then you’re
probably restoring to the same server you backed the files up from – which
is fine you’ll like and want to stick with the defaults. I’m not
saying to get rid of them. I just want the ability to make it LESS WORK than it
is now when I’m not restoring to the same server.

It’s a pain point for me because I have to do it so often and it seems
silly when the computer already knows that the drives specified in the backup
file don’t even exist in the computer to which I’m trying to restore
the file.

What’s the point of making me suffer through manually changing all these
paths?

The restore procedure in Toad is no less complicated than it is in SSMS and I
thought we were looking for ways to make Toad be a Superior solution to SSMS?

Darren
image001.png


#5

Guys,

Out of 1000 database restores for me only 1 would be to the same server.
I’m a working at a software development company and every day I’m
restoring 2-3 different databases to test servers from production servers to
test updates, etc.

If you’re managing databases in your own network, then you’re
probably restoring to the same server you backed the files up from – which
is fine you’ll like and want to stick with the defaults. I’m not
saying to get rid of them. I just want the ability to make it LESS WORK than it
is now when I’m not restoring to the same server.

It’s a pain point for me because I have to do it so often and it seems
silly when the computer already knows that the drives specified in the backup
file don’t even exist in the computer to which I’m trying to restore
the file.

What’s the point of making me suffer through manually changing all these
paths?

The restore procedure in Toad is no less complicated than it is in SSMS and I
thought we were looking for ways to make Toad be a Superior solution to SSMS?

Darren
image001.gif


#6

Darren, Understood and well said.

I have the same issue and understand your request, that is why I decide to use a
script, one for SSMS backups and one for Quest SS TOAD LiteSpeed. So from a
technical perspective I agree, from a Quest marketing point of view, where is
the cost to benefit for the other 99.9% who do not do as you and I do. These are
the guys and gals who set up a backup to run daily and weekly and pray they
never have to restore their production database.

That having been said, Quest usually adds unique feature content such as you
have suggested, so maybe just maybe they will in the case as well.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn. com

678.414.0090 my cell Primary
image001.png


#7

Darren, Understood and well said.

I have the same issue and understand your request, that is why I decide to use a
script, one for SSMS backups and one for Quest SS TOAD LiteSpeed. So from a
technical perspective I agree, from a Quest marketing point of view, where is
the cost to benefit for the other 99.9% who do not do as you and I do. These are
the guys and gals who set up a backup to run daily and weekly and pray they
never have to restore their production database.

That having been said, Quest usually adds unique feature content such as you
have suggested, so maybe just maybe they will in the case as well.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn. com

678.414.0090 my cell Primary
image001.gif


#8

Darren, I can see your point as I have all my databaseson a different drive than the SSMS default and when I do restore databases I dohave to change the path every time. But I thought that this was because thepath to the database files was not contained within the backup file and that iswhy it always went to the SSMS default file location.

But I can see where Hank is coming from and changing thebehavior of this from SSMS might be something that Quest should be cautiousabout because Toad is an extenstion of features of SSMS?

Maybe some kind of selection that allows you to selectthe default SSMS path or the path contained in the actual backup file (if threis one in the file) provided that the path is valid in the new server location?


#9

Sorry about that. Do not try to paste from Outlook into the web
forum…it adds all the text formatting… …

Here is what my response was…

Darren, I can see your point as I have all my databases a different
drive than the SSMS default and when I do restore databases I do have to
change the path every time. But I thought that this was because the path
to the database files was not contained within the backup file and that
is why it always went to the SSMS default file location.

But I can see where Hank is coming from and changing the behavior of
this from SSMS might be something that Quest should be cautious about
because Toad is an extension of features of SSMS?

Maybe some kind of selection that allows you to select the default SSMS
path or the path contained in the actual backup file (if there is one in
the file) provided that the path is valid in the new server location?


#10

As I would also benefit from this feature, I am all for it. I think the
solution is really simple, by default do what SSMS does. However put an option
in the software to override the path in the backup file with the path of the
actual database that the backup file is being restored to when performing a
backup. So for those people out there that expect it to work like SSMS it
will. But for the rest of us who want it to work in a way that makes more
sense, it can too…simply by setting the option.


#11

Excellent !!!

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn. com

678.414.0090 my cell Primary
image001.gif