I'm not sure if this is possible especially since same error will return again. I think you should focus on what original error really was and address that. Once that is done you can drop COPY and do copy-restore again. The thing is that the sequence has to be such that you do restore of logs with NORECOVERY statement until the last log which you restore with RECOVERY (or in your case you would call DB restore with RECOVERY). If something is missing then you must check why it is missing exactly and address that first.
ble1
4 Operator
•
14.4K Posts
0
May 15th, 2011 08:00
I'm not sure if this is possible especially since same error will return again. I think you should focus on what original error really was and address that. Once that is done you can drop COPY and do copy-restore again. The thing is that the sequence has to be such that you do restore of logs with NORECOVERY statement until the last log which you restore with RECOVERY (or in your case you would call DB restore with RECOVERY). If something is missing then you must check why it is missing exactly and address that first.