I've come across an odd situation, and was wondering if anyone can explain what is happening.
I logship from a 2014 server to a 2014 server, putting the database into standby for reporting during the day.
I'm migrating both to new 2019 servers. Initially I have the new secondary server restoring logs from the current 2014 server. As you would expect, you can't put this database into standby.
Then I migrate the source to 2019, and I am now restoring the log backups from the 2019 source server to my secondary.
If I restore the log backup from the new 2019 server WITH NORECOVERY, then do a "RESTORE DATABASE <name> WITH STANDBY...", it fails, telling me it needs to be upgraded.
This is exactly what I would expect to happen.
However, if I do the RESTORE LOG and use the STANDBY option on the log restore, this works and goes into standby mode.
Subsequent log restores then allow me to use the RESTORE DATABASE...WITH STANDBY with no issue.
So, what I'm unsure of is why doing STANDBY on the log restore allows the upgrade to occur, but doing the log restore and then performing the STANDBY fails? I would have thought these would be doing exactly the same thing?