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.
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.
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.
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.
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.
When I design UIs like this I try to eliminate invalid combinations.
User Specifies the name of a database that already exists
These two buttons should be disabled.
The Destination Database Path button should be an event that fires
automatically, (it doesn’t really need to be a button).
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
Specify the name of a database that does not already exist
In this scenario the Destination Database Path button wouldn’t do anything
so it should be disabled. (Or per above, I don’t think that button is
required in the first place because I cannot think of a scenario where a user
would need to click it).
The other two buttons would be enabled. – And yes, I love the addition of
those two buttons!
When I design UIs like this I try to eliminate invalid combinations.
User Specifies the name of a database that already exists
These two buttons should be disabled.
The Destination Database Path button should be an event that fires
automatically, (it doesn’t really need to be a button).
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
Specify the name of a database that does not already exist
In this scenario the Destination Database Path button wouldn’t do anything
so it should be disabled. (Or per above, I don’t think that button is
required in the first place because I cannot think of a scenario where a user
would need to click it).
The other two buttons would be enabled. – And yes, I love the addition of
those two buttons!
When I design UIs like this I try to eliminate invalid combinations.
User Specifies the name of a database that already exists
These two buttons should be disabled.
The Destination Database Path button should be an event that fires
automatically, (it doesn’t really need to be a button).
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
Specify the name of a database that does not already exist
In this scenario the Destination Database Path button wouldn’t do anything
so it should be disabled. (Or per above, I don’t think that button is
required in the first place because I cannot think of a scenario where a user
would need to click it).
The other two buttons would be enabled. – And yes, I love the addition of
those two buttons!
When I design UIs like this I try to eliminate invalid combinations.
User Specifies the name of a database that already exists
These two buttons should be disabled.
The Destination Database Path button should be an event that fires
automatically, (it doesn’t really need to be a button).
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
Specify the name of a database that does not already exist
In this scenario the Destination Database Path button wouldn’t do anything
so it should be disabled. (Or per above, I don’t think that button is
required in the first place because I cannot think of a scenario where a user
would need to click it).
The other two buttons would be enabled. – And yes, I love the addition of
those two buttons!
When I design UIs like this I try to eliminate invalid combinations.
User Specifies the name of a database that already exists
These two buttons should be disabled.
The Destination Database Path button should be an event that fires
automatically, (it doesn’t really need to be a button).
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
Specify the name of a database that does not already exist
In this scenario the Destination Database Path button wouldn’t do anything
so it should be disabled. (Or per above, I don’t think that button is
required in the first place because I cannot think of a scenario where a user
would need to click it).
The other two buttons would be enabled. – And yes, I love the addition of
those two buttons!
When I design UIs like this I try to eliminate invalid combinations.
User Specifies the name of a database that already exists
These two buttons should be disabled.
The Destination Database Path button should be an event that fires
automatically, (it doesn’t really need to be a button).
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
Specify the name of a database that does not already exist
In this scenario the Destination Database Path button wouldn’t do anything
so it should be disabled. (Or per above, I don’t think that button is
required in the first place because I cannot think of a scenario where a user
would need to click it).
The other two buttons would be enabled. – And yes, I love the addition of
those two buttons!
When I design UIs like this I try to eliminate invalid combinations.
User Specifies the name of a database that already exists
These two buttons should be disabled.
The Destination Database Path button should be an event that fires
automatically, (it doesn’t really need to be a button).
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
Specify the name of a database that does not already exist
In this scenario the Destination Database Path button wouldn’t do anything
so it should be disabled. (Or per above, I don’t think that button is
required in the first place because I cannot think of a scenario where a user
would need to click it).
The other two buttons would be enabled. – And yes, I love the addition of
those two buttons!
When I design UIs like this I try to eliminate invalid combinations.
User Specifies the name of a database that already exists
These two buttons should be disabled.
The Destination Database Path button should be an event that fires
automatically, (it doesn’t really need to be a button).
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
Specify the name of a database that does not already exist
In this scenario the Destination Database Path button wouldn’t do anything
so it should be disabled. (Or per above, I don’t think that button is
required in the first place because I cannot think of a scenario where a user
would need to click it).
The other two buttons would be enabled. – And yes, I love the addition of
those two buttons!
Thanks for the answers. Glad you like the proposed buttons.
That is where you are wrong:
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
And the answer to your question is – yes, you can restore db over the same
name as an existing mounted db, but with new mdf, ldf files location.
Here are some proof pics:
But, please note there is an issues in Toad scripting that Recovery State option
scripted as NORECOVERY even if was set to ‘Restore with recovery’
that definitely is wrong and was already fixed on the next version.
Thanks for the answers. Glad you like the proposed buttons.
That is where you are wrong:
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
And the answer to your question is – yes, you can restore db over the same
name as an existing mounted db, but with new mdf, ldf files location.
Here are some proof pics:
But, please note there is an issues in Toad scripting that Recovery State option
scripted as NORECOVERY even if was set to ‘Restore with recovery’
that definitely is wrong and was already fixed on the next version.
Thanks for the answers. Glad you like the proposed buttons.
That is where you are wrong:
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
And the answer to your question is – yes, you can restore db over the same
name as an existing mounted db, but with new mdf, ldf files location.
Here are some proof pics:
But, please note there is an issues in Toad scripting that Recovery State option
scripted as NORECOVERY even if was set to ‘Restore with recovery’
that definitely is wrong and was already fixed on the next version.
Thanks for the answers. Glad you like the proposed buttons.
That is where you are wrong:
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
And the answer to your question is – yes, you can restore db over the same
name as an existing mounted db, but with new mdf, ldf files location.
Here are some proof pics:
But, please note there is an issues in Toad scripting that Recovery State option
scripted as NORECOVERY even if was set to ‘Restore with recovery’
that definitely is wrong and was already fixed on the next version.
Thanks for the answers. Glad you like the proposed buttons.
That is where you are wrong:
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
And the answer to your question is – yes, you can restore db over the same
name as an existing mounted db, but with new mdf, ldf files location.
Here are some proof pics:
But, please note there is an issues in Toad scripting that Recovery State option
scripted as NORECOVERY even if was set to ‘Restore with recovery’
that definitely is wrong and was already fixed on the next version.
Thanks for the answers. Glad you like the proposed buttons.
That is where you are wrong:
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
And the answer to your question is – yes, you can restore db over the same
name as an existing mounted db, but with new mdf, ldf files location.
Here are some proof pics:
But, please note there is an issues in Toad scripting that Recovery State option
scripted as NORECOVERY even if was set to ‘Restore with recovery’
that definitely is wrong and was already fixed on the next version.
Thanks for the answers. Glad you like the proposed buttons.
That is where you are wrong:
I say this because it would be invalid to specify the name of a database that
already exists on the server with any other file paths because it wouldn’t
restore anyway. – Perhaps that’s where I’m wrong? I’ve
not tested that… can you actually restore over the same name as an
existing mounted database, but put the files somewhere else? I don’t think
you can.
And the answer to your question is – yes, you can restore db over the same
name as an existing mounted db, but with new mdf, ldf files location.
Here are some proof pics:
But, please note there is an issues in Toad scripting that Recovery State option
scripted as NORECOVERY even if was set to ‘Restore with recovery’
that definitely is wrong and was already fixed on the next version.
