Issue: Why Restore database wizard/GUI for SQL Server 2014 loading old backup set to restore
I am using SQL server 2014 to restore backups using the GUI, however, the back sets to restore are from old backups that are no longer available along with transaction logs that span months ago.
How can I repair the wizard so that it populates the most recent full and diffs and transaction logs like the way it used to work by default?
Here is a sample screenshot of the of the restore database screen I am making reference to
sql-server sql-server-2014 ssms
asked Oct 17 '17 at 21:14
KefashKefash
1217
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am using SQL server 2014 to restore backups using the GUI, however, the back sets to restore are from old backups that are no longer available along with transaction logs that span months ago.
How can I repair the wizard so that it populates the most recent full and diffs and transaction logs like the way it used to work by default?
Here is a sample screenshot of the of the restore database screen I am making reference to
sql-server sql-server-2014 ssms
asked Oct 17 '17 at 21:14
KefashKefash
1217
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I started answering misunderstanding - but now I'm a bit more confused. Can you post a bit more details? What happens if you restore via script? And are you talking about what's in backup history? Or what happens when you look at a particular backup file and explore what it contains?
– Mike Walsh
Oct 17 '17 at 21:19
Can you post screenshots of the screens where it shows what database backups you can restore, and also if you have 'appended' backups which will put multiple backups in 1 file?
– Ali Razeghi
Oct 17 '17 at 21:28
@MikeWalsh In the area where it says backup set to restore from I get old backups.
– Kefash
Oct 17 '17 at 21:45
add a comment |
I am using SQL server 2014 to restore backups using the GUI, however, the back sets to restore are from old backups that are no longer available along with transaction logs that span months ago.
How can I repair the wizard so that it populates the most recent full and diffs and transaction logs like the way it used to work by default?
Here is a sample screenshot of the of the restore database screen I am making reference to
sql-server sql-server-2014 ssms
asked Oct 17 '17 at 21:14
KefashKefash
1217
I am using SQL server 2014 to restore backups using the GUI, however, the back sets to restore are from old backups that are no longer available along with transaction logs that span months ago.
How can I repair the wizard so that it populates the most recent full and diffs and transaction logs like the way it used to work by default?
Here is a sample screenshot of the of the restore database screen I am making reference to
sql-server sql-server-2014 ssms
sql-server sql-server-2014 ssms
asked Oct 17 '17 at 21:14
KefashKefash
1217
asked Oct 17 '17 at 21:14
KefashKefash
1217
edited Oct 17 '17 at 21:38
Kefash
asked Oct 17 '17 at 21:14
KefashKefash
1217
asked Oct 17 '17 at 21:14
KefashKefash
1217
asked Oct 17 '17 at 21:14
KefashKefash
1217
1217
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 3 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I started answering misunderstanding - but now I'm a bit more confused. Can you post a bit more details? What happens if you restore via script? And are you talking about what's in backup history? Or what happens when you look at a particular backup file and explore what it contains?
– Mike Walsh
Oct 17 '17 at 21:19
Can you post screenshots of the screens where it shows what database backups you can restore, and also if you have 'appended' backups which will put multiple backups in 1 file?
– Ali Razeghi
Oct 17 '17 at 21:28
@MikeWalsh In the area where it says backup set to restore from I get old backups.
– Kefash
Oct 17 '17 at 21:45
add a comment |
I started answering misunderstanding - but now I'm a bit more confused. Can you post a bit more details? What happens if you restore via script? And are you talking about what's in backup history? Or what happens when you look at a particular backup file and explore what it contains?
– Mike Walsh
Oct 17 '17 at 21:19
Can you post screenshots of the screens where it shows what database backups you can restore, and also if you have 'appended' backups which will put multiple backups in 1 file?
– Ali Razeghi
Oct 17 '17 at 21:28
@MikeWalsh In the area where it says backup set to restore from I get old backups.
– Kefash
Oct 17 '17 at 21:45
I started answering misunderstanding - but now I'm a bit more confused. Can you post a bit more details? What happens if you restore via script? And are you talking about what's in backup history? Or what happens when you look at a particular backup file and explore what it contains?
– Mike Walsh
Oct 17 '17 at 21:19
I started answering misunderstanding - but now I'm a bit more confused. Can you post a bit more details? What happens if you restore via script? And are you talking about what's in backup history? Or what happens when you look at a particular backup file and explore what it contains?
– Mike Walsh
Oct 17 '17 at 21:19
Can you post screenshots of the screens where it shows what database backups you can restore, and also if you have 'appended' backups which will put multiple backups in 1 file?
– Ali Razeghi
Oct 17 '17 at 21:28
Can you post screenshots of the screens where it shows what database backups you can restore, and also if you have 'appended' backups which will put multiple backups in 1 file?
– Ali Razeghi
Oct 17 '17 at 21:28
@MikeWalsh In the area where it says backup set to restore from I get old backups.
– Kefash
Oct 17 '17 at 21:45
@MikeWalsh In the area where it says backup set to restore from I get old backups.
– Kefash
Oct 17 '17 at 21:45
add a comment |
1 Answer
1
active
oldest
votes
The Wizard is really just a listing of backup history records in MSDB on that local server. This wizard is not necessary to do backups. In fact, you should run a process to purge backup history on a regular basis. When I do a SQL Server Health Check for a client, I consider it a finding (relatively minor but still a finding) when this history is purged.
I am wondering if you are attempting to restore to a different server which also has that database on it?
Instead, choose Device and browse to your backup file. You'll see the right backupset to restore to inside of that backup file.
The dialog here is sort of a helper if you are restoring on the same server where your SQL Agent backups are taken but if you take backups in different ways, if you clean up history or if you are restoring to a different server, that dialog is likely not so helpful.
answered Oct 17 '17 at 23:00
Mike WalshMike Walsh
14.5k53670
Thanks for the feedback. I get that I can backup using other option. However, the transaction logs can become overwhelming when to script out and in my case, they are taken every 10 mins. Therefore I would use the GUI to script out those many trans logs and apply them on other server or said server. I it may seem minor but if i could somehow repair the GUI to work as it is supposed to that was make my life soooo much easier.
– Kefash
Oct 18 '17 at 22:09
Simple question - are you restoring to the same server the backups are taken from or a different server? If a different server - the GUI isn't broken at all. You might try and do the restore dialog process on the source server and then script it out but don't run and copy/tweak. Also there are myriad scripts out there. I have many clients with frequent log backups and I don't know that I've ever used the GUI to restore those...
– Mike Walsh
Oct 19 '17 at 12:08
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f188703%2fissue-why-restore-database-wizard-gui-for-sql-server-2014-loading-old-backup-se%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The Wizard is really just a listing of backup history records in MSDB on that local server. This wizard is not necessary to do backups. In fact, you should run a process to purge backup history on a regular basis. When I do a SQL Server Health Check for a client, I consider it a finding (relatively minor but still a finding) when this history is purged.
I am wondering if you are attempting to restore to a different server which also has that database on it?
Instead, choose Device and browse to your backup file. You'll see the right backupset to restore to inside of that backup file.
The dialog here is sort of a helper if you are restoring on the same server where your SQL Agent backups are taken but if you take backups in different ways, if you clean up history or if you are restoring to a different server, that dialog is likely not so helpful.
answered Oct 17 '17 at 23:00
Mike WalshMike Walsh
14.5k53670
Thanks for the feedback. I get that I can backup using other option. However, the transaction logs can become overwhelming when to script out and in my case, they are taken every 10 mins. Therefore I would use the GUI to script out those many trans logs and apply them on other server or said server. I it may seem minor but if i could somehow repair the GUI to work as it is supposed to that was make my life soooo much easier.
– Kefash
Oct 18 '17 at 22:09
Simple question - are you restoring to the same server the backups are taken from or a different server? If a different server - the GUI isn't broken at all. You might try and do the restore dialog process on the source server and then script it out but don't run and copy/tweak. Also there are myriad scripts out there. I have many clients with frequent log backups and I don't know that I've ever used the GUI to restore those...
– Mike Walsh
Oct 19 '17 at 12:08
add a comment |
The Wizard is really just a listing of backup history records in MSDB on that local server. This wizard is not necessary to do backups. In fact, you should run a process to purge backup history on a regular basis. When I do a SQL Server Health Check for a client, I consider it a finding (relatively minor but still a finding) when this history is purged.
I am wondering if you are attempting to restore to a different server which also has that database on it?
Instead, choose Device and browse to your backup file. You'll see the right backupset to restore to inside of that backup file.
The dialog here is sort of a helper if you are restoring on the same server where your SQL Agent backups are taken but if you take backups in different ways, if you clean up history or if you are restoring to a different server, that dialog is likely not so helpful.
answered Oct 17 '17 at 23:00
Mike WalshMike Walsh
14.5k53670
Thanks for the feedback. I get that I can backup using other option. However, the transaction logs can become overwhelming when to script out and in my case, they are taken every 10 mins. Therefore I would use the GUI to script out those many trans logs and apply them on other server or said server. I it may seem minor but if i could somehow repair the GUI to work as it is supposed to that was make my life soooo much easier.
– Kefash
Oct 18 '17 at 22:09
Simple question - are you restoring to the same server the backups are taken from or a different server? If a different server - the GUI isn't broken at all. You might try and do the restore dialog process on the source server and then script it out but don't run and copy/tweak. Also there are myriad scripts out there. I have many clients with frequent log backups and I don't know that I've ever used the GUI to restore those...
– Mike Walsh
Oct 19 '17 at 12:08
add a comment |
The Wizard is really just a listing of backup history records in MSDB on that local server. This wizard is not necessary to do backups. In fact, you should run a process to purge backup history on a regular basis. When I do a SQL Server Health Check for a client, I consider it a finding (relatively minor but still a finding) when this history is purged.
I am wondering if you are attempting to restore to a different server which also has that database on it?
Instead, choose Device and browse to your backup file. You'll see the right backupset to restore to inside of that backup file.
The dialog here is sort of a helper if you are restoring on the same server where your SQL Agent backups are taken but if you take backups in different ways, if you clean up history or if you are restoring to a different server, that dialog is likely not so helpful.
answered Oct 17 '17 at 23:00
Mike WalshMike Walsh
14.5k53670
The Wizard is really just a listing of backup history records in MSDB on that local server. This wizard is not necessary to do backups. In fact, you should run a process to purge backup history on a regular basis. When I do a SQL Server Health Check for a client, I consider it a finding (relatively minor but still a finding) when this history is purged.
I am wondering if you are attempting to restore to a different server which also has that database on it?
Instead, choose Device and browse to your backup file. You'll see the right backupset to restore to inside of that backup file.
The dialog here is sort of a helper if you are restoring on the same server where your SQL Agent backups are taken but if you take backups in different ways, if you clean up history or if you are restoring to a different server, that dialog is likely not so helpful.
answered Oct 17 '17 at 23:00
Mike WalshMike Walsh
14.5k53670
answered Oct 17 '17 at 23:00
Mike WalshMike Walsh
14.5k53670
answered Oct 17 '17 at 23:00
Mike WalshMike Walsh
14.5k53670
answered Oct 17 '17 at 23:00
Mike WalshMike Walsh
14.5k53670
14.5k53670
Thanks for the feedback. I get that I can backup using other option. However, the transaction logs can become overwhelming when to script out and in my case, they are taken every 10 mins. Therefore I would use the GUI to script out those many trans logs and apply them on other server or said server. I it may seem minor but if i could somehow repair the GUI to work as it is supposed to that was make my life soooo much easier.
– Kefash
Oct 18 '17 at 22:09
Simple question - are you restoring to the same server the backups are taken from or a different server? If a different server - the GUI isn't broken at all. You might try and do the restore dialog process on the source server and then script it out but don't run and copy/tweak. Also there are myriad scripts out there. I have many clients with frequent log backups and I don't know that I've ever used the GUI to restore those...
– Mike Walsh
Oct 19 '17 at 12:08
add a comment |
Thanks for the feedback. I get that I can backup using other option. However, the transaction logs can become overwhelming when to script out and in my case, they are taken every 10 mins. Therefore I would use the GUI to script out those many trans logs and apply them on other server or said server. I it may seem minor but if i could somehow repair the GUI to work as it is supposed to that was make my life soooo much easier.
– Kefash
Oct 18 '17 at 22:09
Simple question - are you restoring to the same server the backups are taken from or a different server? If a different server - the GUI isn't broken at all. You might try and do the restore dialog process on the source server and then script it out but don't run and copy/tweak. Also there are myriad scripts out there. I have many clients with frequent log backups and I don't know that I've ever used the GUI to restore those...
– Mike Walsh
Oct 19 '17 at 12:08
Thanks for the feedback. I get that I can backup using other option. However, the transaction logs can become overwhelming when to script out and in my case, they are taken every 10 mins. Therefore I would use the GUI to script out those many trans logs and apply them on other server or said server. I it may seem minor but if i could somehow repair the GUI to work as it is supposed to that was make my life soooo much easier.
– Kefash
Oct 18 '17 at 22:09
Thanks for the feedback. I get that I can backup using other option. However, the transaction logs can become overwhelming when to script out and in my case, they are taken every 10 mins. Therefore I would use the GUI to script out those many trans logs and apply them on other server or said server. I it may seem minor but if i could somehow repair the GUI to work as it is supposed to that was make my life soooo much easier.
– Kefash
Oct 18 '17 at 22:09
Simple question - are you restoring to the same server the backups are taken from or a different server? If a different server - the GUI isn't broken at all. You might try and do the restore dialog process on the source server and then script it out but don't run and copy/tweak. Also there are myriad scripts out there. I have many clients with frequent log backups and I don't know that I've ever used the GUI to restore those...
– Mike Walsh
Oct 19 '17 at 12:08
Simple question - are you restoring to the same server the backups are taken from or a different server? If a different server - the GUI isn't broken at all. You might try and do the restore dialog process on the source server and then script it out but don't run and copy/tweak. Also there are myriad scripts out there. I have many clients with frequent log backups and I don't know that I've ever used the GUI to restore those...
– Mike Walsh
Oct 19 '17 at 12:08
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f188703%2fissue-why-restore-database-wizard-gui-for-sql-server-2014-loading-old-backup-se%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I started answering misunderstanding - but now I'm a bit more confused. Can you post a bit more details? What happens if you restore via script? And are you talking about what's in backup history? Or what happens when you look at a particular backup file and explore what it contains?
– Mike Walsh
Oct 17 '17 at 21:19
Can you post screenshots of the screens where it shows what database backups you can restore, and also if you have 'appended' backups which will put multiple backups in 1 file?
– Ali Razeghi
Oct 17 '17 at 21:28
@MikeWalsh In the area where it says backup set to restore from I get old backups.
– Kefash
Oct 17 '17 at 21:45