if you remember that backup you have taken is full then you can chage the extension to .bak instead of .trn.

copy job will not make any mix up with restore.

the only thing you need to make sure that you doing the restoration in sequence.

lastest full backup

latest diff backup(if applicable)

start from...

ok, so if the database was properly detached then you will be able to attach them.

whats the problem/error you getting while attaching the files?

Also try to attach with original...

i will suggest reconfigure the log shipping for that perticular database.

the new database have new definition and you mixed the definition with old mdf....and sql is totally not able to understand the definition from the replaced mdf file.

if you have...

if you not able to attach it, it could be because it was not properly detached.

do you the database somewhere still?

yes, it will be same.

whenever you want to change to norecovery, simply restore ...... with norecovery and then if you change your mind, simply restore log with standby... and so...

your database is already in standby mode which means as well in norecovery mode.

So let it be in standby mode because it will help you in 2 way :-

1) will...

have you tried to change the backup location to some other drive or the drive where you already taking the daily backup.

When you restoring the last log,

replace occurrence of "WITH NORECOVERY" with "WITH STANDBY = [some _filename]".

[some_filename] = you can mention as 'c:\undo.txt' or whatever....

what do you mean by norecovery, your database already in norecovery mode as its in standby mode.

be familiar with the term of recovery and norecovery on below link

http://msdn.microsoft.com/en-us/library/ms177446.aspx

instead of directly blaming the sql for the slowness, you need to find

1) is application slow for all users?

2) is the network itsellf working fine?

3) If application is accessed by...

i think the problem is with select statement

try with

select '''£''' from......

so three ' before and after £

when you restore the last log from primary to secondary, you have to provide the option as 'with standby'.

It will make your secondary server database in standby mode and...

then what is the meaning of your secondary if you have to restore this much?