Hi all,

I have a stored-procedure running on an SQL2k5 box which is updating a table on a SQL2k linked server.

I have ensured that the "Collation Comaptible" optiions are set True...

....Actually,red-herring, it was coallation conflict as Paul Mu suggested! (thanks Paul)

Not removed the login/role configuration and retested as prodution has now started and next window is a while away!

cheers

Thanks Pradeep, i was experiencing similar problems when replicating from 2000 to 2005 and it was simply a case of adding the login and configuring server roles as you mentioned.

Why...

As far as I'm aware transactional replication is one-way; in order to have two-way replication between SQL servers you need to be looking at merge replication...

The potential for conflicting transactions...

I would question the reliability of the SET ROWCOUNT @n...

.. unless of course it's a problem with SELECT TOP n, i've just tried both methods with the exact same query...

the idea was to create a covering index...

doh! - answered my own question - didn't notice they were nvarchar!!! (didn't get much sleep last night!)

I can't see how 500 + 80 + 8 + 4 bytes exceeds the 900 byte limit for indexes.

Am I missing something here?

Couldn't agree more...

One more lesson learnt though - I chose the size of the varchar column arbitrarily at 8000 - whereas this actually tips the potential row size over the...

Thanks Robert,

I've created another table on the reporting server which is populated with the ID column and the first 20 characters of the varchar(8000) column -I'll run a scheduled transfer...

An update for all those who were so kind as to contribute....

I converted said column to varchar(8000) on Sunday night and it was fairly pain-free, although 2am is a bit...

Many thanks for the reassuring replies - I am about to convert the text column to a varchar - it could be a long night!!!

I am working on a problem of replication from Spain to UK and this article makes interesting reading...thanks go to the author

Derek: If you want a perfect copy of the...

Further information regarding the SARG issue can be found on this site, search for "Beware of Search Argument (SARG) Data Types"....

...One other thing - you didn't mention what version of SQL Server you are running;

If it is SQL2K then for Log-Shipping you can avoid the extra licencing cost of Enterprise...