Toad World® Forums

Feature Request: Restore Backup - Auto Select file when only one file


#1

When choosing the option to restore a database from a file, after you select the
file, if the file only contains one backup, could you please auto-select that
file for restore so we don’t have to do it manually?

In the example above, I’ve had to do these actions:

Steps I have to do to Restore a File

Feature Request to make it take less time

image004.png

image002.jpeg


#2

Hello Darren,

I have thoroughly considered your request and I DO NOT AGREE or DIS-AGREE with
it as of this email… It did raise the graying hairs of experience on the
back of my head as a potential benefit to future problem issue. So please hear
me out, by reading the below.

I respectfully, request that you consider what you are asking here in light of
the fact that the backup is a function of the MS database version or some other
software such as Quest LiteSpeed for SQL Server. I am not sure, that Quest is
where this must be asked. I believe your suggestion, just placed on the table
and then looked upon, has merit. However, since I am doing several backup and
restores as part of release builds, I am having a hard time separating the
software option you asked for with the responsibility of the user.

You sir are well versed in this process, but a newbie to SQL Server and Quest
Toad-SS or Quest LiteSpeed, might make a mistake and if that does happen then
there will be issues of liability and finger pointing the Quest deviated away
from Microsoft best practices in this very specific area.

Personally, I take your suggestion/instruct ions seriously and I am not
diminishing the need, I am just worried about some un-intended consequences of
your request in the wrong hands.

I teach all Product Support and operations folks to not only enter in the
correct info, but to printout and validate the backup/restore script so as to
submit same and part of their operations documentation. This may sound like an
overkill, but since the default action or S.O.P.(rocess) currently allows for
the restore SQL Statement to be reviewed only if the user selects the ‘SQL
Script’, then I respectfully request that TOAD-SS also do a Quest
LiteSpeed 5.2 does here on backups and that is to show this final SQL Script as
part of a validation box.

At the end of the day, this is not my call. However, I have written the above in
order to stir your thoughts as well as others so as to see if there are really
any true issues with this request.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn. com

678.414.0090 my cell Primary
image002.jpeg


#3

Hello Darren,

I have thoroughly considered your request and I DO NOT AGREE or DIS-AGREE with
it as of this email… It did raise the graying hairs of experience on the
back of my head as a potential benefit to future problem issue. So please hear
me out, by reading the below.

I respectfully, request that you consider what you are asking here in light of
the fact that the backup is a function of the MS database version or some other
software such as Quest LiteSpeed for SQL Server. I am not sure, that Quest is
where this must be asked. I believe your suggestion, just placed on the table
and then looked upon, has merit. However, since I am doing several backup and
restores as part of release builds, I am having a hard time separating the
software option you asked for with the responsibility of the user.

You sir are well versed in this process, but a newbie to SQL Server and Quest
Toad-SS or Quest LiteSpeed, might make a mistake and if that does happen then
there will be issues of liability and finger pointing the Quest deviated away
from Microsoft best practices in this very specific area.

Personally, I take your suggestion/instruct ions seriously and I am not
diminishing the need, I am just worried about some un-intended consequences of
your request in the wrong hands.

I teach all Product Support and operations folks to not only enter in the
correct info, but to printout and validate the backup/restore script so as to
submit same and part of their operations documentation. This may sound like an
overkill, but since the default action or S.O.P.(rocess) currently allows for
the restore SQL Statement to be reviewed only if the user selects the ‘SQL
Script’, then I respectfully request that TOAD-SS also do a Quest
LiteSpeed 5.2 does here on backups and that is to show this final SQL Script as
part of a validation box.

At the end of the day, this is not my call. However, I have written the above in
order to stir your thoughts as well as others so as to see if there are really
any true issues with this request.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn. com

678.414.0090 my cell Primary
image001.gif


#4

Hello Darren,

I have thoroughly considered your request and I DO NOT AGREE or DIS-AGREE with
it as of this email… It did raise the graying hairs of experience on the
back of my head as a potential benefit to future problem issue. So please hear
me out, by reading the below.

I respectfully, request that you consider what you are asking here in light of
the fact that the backup is a function of the MS database version or some other
software such as Quest LiteSpeed for SQL Server. I am not sure, that Quest is
where this must be asked. I believe your suggestion, just placed on the table
and then looked upon, has merit. However, since I am doing several backup and
restores as part of release builds, I am having a hard time separating the
software option you asked for with the responsibility of the user.

You sir are well versed in this process, but a newbie to SQL Server and Quest
Toad-SS or Quest LiteSpeed, might make a mistake and if that does happen then
there will be issues of liability and finger pointing the Quest deviated away
from Microsoft best practices in this very specific area.

Personally, I take your suggestion/instruct ions seriously and I am not
diminishing the need, I am just worried about some un-intended consequences of
your request in the wrong hands.

I teach all Product Support and operations folks to not only enter in the
correct info, but to printout and validate the backup/restore script so as to
submit same and part of their operations documentation. This may sound like an
overkill, but since the default action or S.O.P.(rocess) currently allows for
the restore SQL Statement to be reviewed only if the user selects the ‘SQL
Script’, then I respectfully request that TOAD-SS also do a Quest
LiteSpeed 5.2 does here on backups and that is to show this final SQL Script as
part of a validation box.

At the end of the day, this is not my call. However, I have written the above in
order to stir your thoughts as well as others so as to see if there are really
any true issues with this request.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn. com

678.414.0090 my cell Primary


#5

Hello Darren & Hank,

From my point of view the majority of what Darren is asking for is the ability
to establish dialog defaults. While I don’t use the restore feature in
Toad very often, I would see the value in being able to establish dialog
defaults for other dialogs. If new person to Toad went in and established a
irregular defaults for their restore database dialog and didn’t know what
they were doing…well…I don’t know what you can do other than
say “Don’t do that” I don’t see it as an issue of
liability.

Another thought I had, is if a user is doing the same type of restore
frequently, why not take a copy of the SQL Script and use this to automate the
operation?

But yet another thought I had regarding database restores, which I normally do
in Management Studio instead of Toad, is if Toad could be smart enough to know
that when I am restoring a backup from a file to a database on my SQL server, to
automatically change the path to the existing MDF, LDF of the database I chose
to restore to instead of the path of the database that the backup originally
came from. I never recall a moment when I was restored from a file to a database
that I wanted the path to the MDF/LDF specified in the file INSTEAD of the
actual ones for the database I am restoring to…especially when I have
chosen the option to OVERWRITE the existing database. If you could make Toad do
this behavior I would NEVER use Management Studio again to do to restore again.

Btw, I have a feature request: Can you give me the option to NOT see the error
messages that come up when Intellisense goes haywire? These get annoying and I
don’t always want to restart Toad to get back in a mode where me typing in
an Editor is not causing error messages to come up. With every version
Intellisense gets better and the frequency of these errors is less, but they
still happen and they will still happen in the production version. And
it’s annoying….really, really annoying. If anything give me the
option to send them to a log file instead of showing them to me. (btw, I
haven’t had an issue like this with .133 so far!)

Thanks,

Kent


#6

Hello Darren & Hank,

From my point of view the majority of what Darren is asking for is the ability
to establish dialog defaults. While I don’t use the restore feature in
Toad very often, I would see the value in being able to establish dialog
defaults for other dialogs. If new person to Toad went in and established a
irregular defaults for their restore database dialog and didn’t know what
they were doing…well…I don’t know what you can do other than
say “Don’t do that” I don’t see it as an issue of
liability.

Another thought I had, is if a user is doing the same type of restore
frequently, why not take a copy of the SQL Script and use this to automate the
operation?

But yet another thought I had regarding database restores, which I normally do
in Management Studio instead of Toad, is if Toad could be smart enough to know
that when I am restoring a backup from a file to a database on my SQL server, to
automatically change the path to the existing MDF, LDF of the database I chose
to restore to instead of the path of the database that the backup originally
came from. I never recall a moment when I was restored from a file to a database
that I wanted the path to the MDF/LDF specified in the file INSTEAD of the
actual ones for the database I am restoring to…especially when I have
chosen the option to OVERWRITE the existing database. If you could make Toad do
this behavior I would NEVER use Management Studio again to do to restore again.

Btw, I have a feature request: Can you give me the option to NOT see the error
messages that come up when Intellisense goes haywire? These get annoying and I
don’t always want to restart Toad to get back in a mode where me typing in
an Editor is not causing error messages to come up. With every version
Intellisense gets better and the frequency of these errors is less, but they
still happen and they will still happen in the production version. And
it’s annoying….really, really annoying. If anything give me the
option to send them to a log file instead of showing them to me. (btw, I
haven’t had an issue like this with .133 so far!)

Thanks,

Kent
image001.gif


#7

Hello Darren & Hank,

From my point of view the majority of what Darren is asking for is the ability
to establish dialog defaults. While I don’t use the restore feature in
Toad very often, I would see the value in being able to establish dialog
defaults for other dialogs. If new person to Toad went in and established a
irregular defaults for their restore database dialog and didn’t know what
they were doing…well…I don’t know what you can do other than
say “Don’t do that” I don’t see it as an issue of
liability.

Another thought I had, is if a user is doing the same type of restore
frequently, why not take a copy of the SQL Script and use this to automate the
operation?

But yet another thought I had regarding database restores, which I normally do
in Management Studio instead of Toad, is if Toad could be smart enough to know
that when I am restoring a backup from a file to a database on my SQL server, to
automatically change the path to the existing MDF, LDF of the database I chose
to restore to instead of the path of the database that the backup originally
came from. I never recall a moment when I was restored from a file to a database
that I wanted the path to the MDF/LDF specified in the file INSTEAD of the
actual ones for the database I am restoring to…especially when I have
chosen the option to OVERWRITE the existing database. If you could make Toad do
this behavior I would NEVER use Management Studio again to do to restore again.

Btw, I have a feature request: Can you give me the option to NOT see the error
messages that come up when Intellisense goes haywire? These get annoying and I
don’t always want to restart Toad to get back in a mode where me typing in
an Editor is not causing error messages to come up. With every version
Intellisense gets better and the frequency of these errors is less, but they
still happen and they will still happen in the production version. And
it’s annoying….really, really annoying. If anything give me the
option to send them to a log file instead of showing them to me. (btw, I
haven’t had an issue like this with .133 so far!)

Thanks,

Kent
image002.jpeg


#8

Kent,

Your statement, I concur !

I use the script more times than not and forgot to put something like your
comment in my original response.

@Kent à Another thought I had, is if a user is doing the same type of restore
frequently, why not take a copy of the SQL Script and use this to automate the
operation?

Lastly, please open up a separate Intellisense post, I have issue there as well
and I about to report it for corrective action.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn. com

678.414.0090 my cell Primary
image002.jpeg


#9

Kent,

Your statement, I concur !

I use the script more times than not and forgot to put something like your
comment in my original response.

@Kent à Another thought I had, is if a user is doing the same type of restore
frequently, why not take a copy of the SQL Script and use this to automate the
operation?

Lastly, please open up a separate Intellisense post, I have issue there as well
and I about to report it for corrective action.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn. com

678.414.0090 my cell Primary


#10

Kent,

Your statement, I concur !

I use the script more times than not and forgot to put something like your
comment in my original response.

@Kent à Another thought I had, is if a user is doing the same type of restore
frequently, why not take a copy of the SQL Script and use this to automate the
operation?

Lastly, please open up a separate Intellisense post, I have issue there as well
and I about to report it for corrective action.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn. com

678.414.0090 my cell Primary
image001.gif


#11

The script approach doesn’t really work because I’m almost never
restoring the same database. The database names are always different, the
source files in different locations, etc.

My issue isn’t with the selection of the files to restore, it’s with
the destination and the manually having to change the info stored in the file
when restoring to servers that aren’t the production server.

Darren
image002.jpeg


#12

The script approach doesn’t really work because I’m almost never
restoring the same database. The database names are always different, the
source files in different locations, etc.

My issue isn’t with the selection of the files to restore, it’s with
the destination and the manually having to change the info stored in the file
when restoring to servers that aren’t the production server.

Darren
image001.gif


#13

The script approach doesn’t really work because I’m almost never
restoring the same database. The database names are always different, the
source files in different locations, etc.

My issue isn’t with the selection of the files to restore, it’s with
the destination and the manually having to change the info stored in the file
when restoring to servers that aren’t the production server.

Darren