August 20, 2019 at 6:33 pm
There are some similar errors with some versions of SSMS. Try to use t-sql instead of SSMS and see if it works. If it errors, you should get more information than what you get with SSMS. Also check the differential and make sure it isn't corrupt - do a restore headeronly on the file and see if you get any errors. You'd also want to check the permissions on the file to make sure there aren't any issues with those.
Sue
August 21, 2019 at 4:51 pm
I know I can use the script, but SSMS is a tool that is used so often , you can also generate script from there.
But I just want to know if this is a bug of SSMS, if so, it should fixed.
I downloaded the newer version 18.2, it is the same error.
Actually I tried on the production server itself, same error.
But if I use SSMS to restore to a point of time, it chose the same full and differential backup, and it restores OK with no error.
August 22, 2019 at 5:09 pm
There are way too many bugs in SSMS so I can't remember which versions have which issues and they can disappear and reappear in different versions.You can search for them or file a new report using User Voice, feedback or whatever they are calling it this month:
https://feedback.azure.com/forums/908035-sql-server
Part of the reason for trying in t-sql was for the error message. You can often get more information if trying in t-sql. I didn't write the product, it is what it is.
August 22, 2019 at 10:07 pm
You might want to create a small test database, take a full backup, then a differential, then restore both - to tell whether a failure you are seeing is due to a corrrupted backup, or wrong method/bug in SSMS.
http://90.212.51.111 domain
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply