Well, that does not help much.

I know the steps to restore to another server, but on the same server, overwrite the same database, do I also need to go through...

No it is not a copy only backup.

What is  the strange thing is I query the  backup history, the older one is no longer in msdb database, for we purge...

Note the wrong version it pulled is a full backup I did manually , not the sql agent job triggered jobs.

I just tried the restore  steps on another server with 17.4 installed, it restored the  correct version.

And then I  tried on another server that  has  SSMS 18.4 installed, it restored...

Good suggestions. I will try that.

The restore wizard pulls the backup that I did manually earlier,  it is in the msdn database.

Thank you all!

Thanks, that is what I am thinking too. We are not using the new features.

And Only when we need to move to a new instance, then we can upgrade

Thanks, yes, that is mostly I did.

When I asked the database model or Relationship from the vendor, they did not reply to me. I suppose they would not like us...

Hi Paul,

Did set the isolation level is only available in Enterprise edition? I cannot find the information online.

Did that also require a reboot? I changed for my standard edition without...

Did you ever find the solution, I have the same issue,

Thanks

Hi Paul,

Did  you change the isolation level for reportserver db or reportServerTemp db?

We also have a lot of blocks and locks in the database.

I found out the account actually does have read access to the directory.

I tested to ask somebody not in our team but in same department  to see if she can...

Thanks, figured out the access issue

The strange thing is that the service account does not have access to a share, but it still can access the file.

Thank you!

I will remember that if I just install SSMS, will also install sqlcmd separately.