March 8, 2019 at 1:36 pm
Hello!
I am restoring databases from SQL 2012 backup(full, differential and logs) to SQL 2016.
If I restore the database on SQL 2016 with just full or just differential it works fine, but when I restore full with norecovery and try to apply differential I get the following error message:
"no full database backup is selected to be restored "
Thank you.
March 8, 2019 at 4:24 pm
PJ_SQL - Friday, March 8, 2019 1:36 PMHello!I am restoring databases from SQL 2012 backup(full, differential and logs) to SQL 2016.
If I restore the database on SQL 2016 with just full or just differential it works fine, but when I restore full with norecovery and try to apply differential I get the following error message:
"no full database backup is selected to be restored "Thank you.
You'll get that error when the sequence of the restores is incorrect - such as restoring a differential previous to the full backup that was restored.
So you will want to go through the order of the backup files and make sure you are restoring in the correct order, the correct differential.
Sue
March 8, 2019 at 10:12 pm
PJ_SQL - Friday, March 8, 2019 1:36 PMHello!I am restoring databases from SQL 2012 backup(full, differential and logs) to SQL 2016.
If I restore the database on SQL 2016 with just full or just differential it works fine, but when I restore full with norecovery and try to apply differential I get the following error message:
"no full database backup is selected to be restored "Thank you.
Can you try T-SQL and find what is actual error msg.
https://www.sqlserverblogforum.com/backuprestore/step-by-step-backuprestore-using-t-sql/
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
March 11, 2019 at 5:18 am
PJ_SQL - Friday, March 8, 2019 1:36 PMHello!I am restoring databases from SQL 2012 backup(full, differential and logs) to SQL 2016.
If I restore the database on SQL 2016 with just full or just differential it works fine, but when I restore full with norecovery and try to apply differential I get the following error message:
"no full database backup is selected to be restored "Thank you.
In addition to the other comments above, I've found this is a bug in SSMS17. If I try to restore via the GUI (even when I've definitely got the LSN chain correct) I often get this error message, but if I use T-SQL for exactly the same files, it works. Don't know why!
March 11, 2019 at 12:19 pm
I agree with Beatrix. I was able to restore using T-SQL instead trying from GUI>
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply