A few random thoughts:-

Transactional replication doesn't render your reporting database unwritable, so you are probably able to make changes there already.

Unless you are using immediate upating, there's going to be...

Thanks Paul... I still have a long way to go to catch you up ...in both number of posts and sheer depth...

Not up to your usual bulletproof solutions Paul;-)

INSERT dbo.SingleRowOnly (data) VALUES ('A'); -- Succeeds

insert enforcesinglerow (row_id) values(2)

INSERT dbo.SingleRowOnly (data) VALUES ('B'); -- Now it works

If you want to make sure no more than 1 record is created in the table, you could do this:-

CREATE TABLE OneRecordOnly(Id int ,

...

Partly correct...SQL89 INNER JOINs are still supported, so this is valid

SELECT t1.id as id1, t1.name1...

If you only want to know the keys of the duplicate rows, then you can do:-

SELECT cola, colb, colc, count(*)

FROM NonUnique

GROUP BY cola, colb, colc

HAVING count(*) > 1

4. Applied the unapplied transaction log backups in sequence to the secondary database Mydb (Except the tail log backup, mydb_Tail.trn , because I did NOT understand whether I need to...

Wrong program... the avatar is actually Captain Scarlet (but Thunderbirds was much better):-)

Try setting the -QueryTimeout parameter on Invoke-SqlCmd .

Fiddling with 'remote login timeout' etc isn't going to help here, it's probably logging in quickly enough, it's just the actual query (BACKUP...)...

Are you sure the first query completed successfully?

Sounds as though it's failing before it gets to the bit where it does the N+1 at the end.

Thanks Ian. So based on your reply I understand that in Bulk-Logged mode the Tlog backup will be slower, because it is during this backup that the full detail changes...

What you suspect is true.

To be able to restore your database to a point in time, you need to know exactly what changes have been made since your last full...

I realise I've joined this thread a bit late, so may have missed something when skimming through the other replies, but...

The OLE DB provider "SQLNCLI" for linked server "support \...

I posted a similar question a few months ago... you may want to have a look at some of the suggestions there

http://www.sqlservercentral.com/Forums/Topic766956-61-1.aspx

Thanks Mr Brew:-)