Toad World® Forums

Restore Database - Overwrite option does not auto-select file paths

Restore Database - Overwrite option does not
auto-select file paths

Darren, Hank

We investigated this in details and see that now in 5.6 Toad displays not
accurate data in Restore As column. In some cases you see paths from backup, in
others actual restore paths. But If you don’t see any MOVE statement in
the resulted script - Server will try to Restore backup to the same files as DB
already has. Double checked in Management Studio – the same behavior.

Please note – there is no relation between Replace option. It just
resolved as REPLACE clause in the script.

That is why you were confused.

As result we came up to this solution: Always display what will be really used
during restore operation at Restore As column. We add three new buttons in
compare to 5.6 version. We are thinking about these labels:

Destination Database Path – get from selected database, that exist on
servers. Will be disabled for new databases.

Backup Path – get paths from backup

SQL Server Defaults – set defaults from for this Server Instance

How that sounds to you?

regards,

Alexander Maximov

Darren, Hank

We investigated this in details and see that now in 5.6 Toad displays not
accurate data in Restore As column. In some cases you see paths from backup, in
others actual restore paths. But If you don’t see any MOVE statement in
the resulted script - Server will try to Restore backup to the same files as DB
already has. Double checked in Management Studio – the same behavior.

Please note – there is no relation between Replace option. It just
resolved as REPLACE clause in the script.

That is why you were confused.

As result we came up to this solution: Always display what will be really used
during restore operation at Restore As column. We add three new buttons in
compare to 5.6 version. We are thinking about these labels:

Destination Database Path – get from selected database, that exist on
servers. Will be disabled for new databases.

Backup Path – get paths from backup

SQL Server Defaults – set defaults from for this Server Instance

How that sounds to you?

regards,

Alexander Maximov
image002.jpeg

Darren, Hank

We investigated this in details and see that now in 5.6 Toad displays not
accurate data in Restore As column. In some cases you see paths from backup, in
others actual restore paths. But If you don’t see any MOVE statement in
the resulted script - Server will try to Restore backup to the same files as DB
already has. Double checked in Management Studio – the same behavior.

Please note – there is no relation between Replace option. It just
resolved as REPLACE clause in the script.

That is why you were confused.

As result we came up to this solution: Always display what will be really used
during restore operation at Restore As column. We add three new buttons in
compare to 5.6 version. We are thinking about these labels:

Destination Database Path – get from selected database, that exist on
servers. Will be disabled for new databases.

Backup Path – get paths from backup

SQL Server Defaults – set defaults from for this Server Instance

How that sounds to you?

regards,

Alexander Maximov
image001.gif

Darren, Hank

We investigated this in details and see that now in 5.6 Toad displays not
accurate data in Restore As column. In some cases you see paths from backup, in
others actual restore paths. But If you don’t see any MOVE statement in
the resulted script - Server will try to Restore backup to the same files as DB
already has. Double checked in Management Studio – the same behavior.

Please note – there is no relation between Replace option. It just
resolved as REPLACE clause in the script.

That is why you were confused.

As result we came up to this solution: Always display what will be really used
during restore operation at Restore As column. We add three new buttons in
compare to 5.6 version. We are thinking about these labels:

Destination Database Path – get from selected database, that exist on
servers. Will be disabled for new databases.

Backup Path – get paths from backup

SQL Server Defaults – set defaults from for this Server Instance

How that sounds to you?

regards,

Alexander Maximov
image006.jpeg

Darren, Hank

We investigated this in details and see that now in 5.6 Toad displays not
accurate data in Restore As column. In some cases you see paths from backup, in
others actual restore paths. But If you don’t see any MOVE statement in
the resulted script - Server will try to Restore backup to the same files as DB
already has. Double checked in Management Studio – the same behavior.

Please note – there is no relation between Replace option. It just
resolved as REPLACE clause in the script.

That is why you were confused.

As result we came up to this solution: Always display what will be really used
during restore operation at Restore As column. We add three new buttons in
compare to 5.6 version. We are thinking about these labels:

Destination Database Path – get from selected database, that exist on
servers. Will be disabled for new databases.

Backup Path – get paths from backup

SQL Server Defaults – set defaults from for this Server Instance

How that sounds to you?

regards,

Alexander Maximov

Darren, Hank

We investigated this in details and see that now in 5.6 Toad displays not
accurate data in Restore As column. In some cases you see paths from backup, in
others actual restore paths. But If you don’t see any MOVE statement in
the resulted script - Server will try to Restore backup to the same files as DB
already has. Double checked in Management Studio – the same behavior.

Please note – there is no relation between Replace option. It just
resolved as REPLACE clause in the script.

That is why you were confused.

As result we came up to this solution: Always display what will be really used
during restore operation at Restore As column. We add three new buttons in
compare to 5.6 version. We are thinking about these labels:

Destination Database Path – get from selected database, that exist on
servers. Will be disabled for new databases.

Backup Path – get paths from backup

SQL Server Defaults – set defaults from for this Server Instance

How that sounds to you?

regards,

Alexander Maximov
image007.jpeg

Alex, I will look at this more closely tonight or over the weekend, when will
the beta be ready for Tester?

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary

Hank.Freeman50 (Skype)
image007.jpeg

Alex, I will look at this more closely tonight or over the weekend, when will
the beta be ready for Tester?

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary

Hank.Freeman50 (Skype)
image001.gif

Alex, I will look at this more closely tonight or over the weekend, when will
the beta be ready for Tester?

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary

Hank.Freeman50 (Skype)

Alex, I will look at this more closely tonight or over the weekend, when will
the beta be ready for Tester?

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary

Hank.Freeman50 (Skype)

Alex, I will look at this more closely tonight or over the weekend, when will
the beta be ready for Tester?

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary

Hank.Freeman50 (Skype)
image002.jpeg

Alex, I will look at this more closely tonight or over the weekend, when will
the beta be ready for Tester?

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary

Hank.Freeman50 (Skype)
image006.jpeg

Any feedback will be appreciated. It is not decided yet about beginning of Beta
program, don’t want to give you wrong estimates for now.

regards,

Alexander Maximov
image007.jpeg

Any feedback will be appreciated. It is not decided yet about beginning of Beta
program, don’t want to give you wrong estimates for now.

regards,

Alexander Maximov
image006.jpeg

Any feedback will be appreciated. It is not decided yet about beginning of Beta
program, don’t want to give you wrong estimates for now.

regards,

Alexander Maximov

Any feedback will be appreciated. It is not decided yet about beginning of Beta
program, don’t want to give you wrong estimates for now.

regards,

Alexander Maximov

Any feedback will be appreciated. It is not decided yet about beginning of Beta
program, don’t want to give you wrong estimates for now.

regards,

Alexander Maximov
image002.jpeg

Any feedback will be appreciated. It is not decided yet about beginning of Beta
program, don’t want to give you wrong estimates for now.

regards,

Alexander Maximov
image001.gif

Thanks Alex!

I’d rather have a strong beta presented by Quest than one that is an Alpha
release .

I am going to take a chance here with the following, which I had previously
shared with some mutual friends.

I would like to share with you something I recently found and have brought to
the table where I work as well have brought to the attention of others vendors
NOT ASSOCIATED with Quest. I hope you find it enlightening and not pointed and
any one person or group within Quest.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary

Hank.Freeman50 (Skype)
image002.jpeg