You might get away with doing a BACKUP using the NORECOVERY option followed by a RESTORE WITH STANDBY - this is not supported in the GUI itself however you can copy the script and run it it SSMS/QA adding NORECOVERY to the script.
If this does not put the database back into a state where logs can be restored to it then you would need to do a full backup of the source database and restore that to the destination database using STANDBY.
It really depends on what SQL Server thinks has happened to the database since it was detached/attached as to wheter it will let you do option 1. Option 2 will ofcourse work regardless of the state of the destination database.
HTH,
- James
James Moore
Head of DBA Tools
Red Gate Software Ltd
JanPoot
Posts: 5
Comments
You might get away with doing a BACKUP using the NORECOVERY option followed by a RESTORE WITH STANDBY - this is not supported in the GUI itself however you can copy the script and run it it SSMS/QA adding NORECOVERY to the script.
If this does not put the database back into a state where logs can be restored to it then you would need to do a full backup of the source database and restore that to the destination database using STANDBY.
It really depends on what SQL Server thinks has happened to the database since it was detached/attached as to wheter it will let you do option 1. Option 2 will ofcourse work regardless of the state of the destination database.
HTH,
- James
Head of DBA Tools
Red Gate Software Ltd