That's good news...

Instead of altering the column, you can just create a new column copy the data.  drop the old column add it again (to maintain the column name, with the correct...

A quick follow-up...

I setup merge replication, and looked at the procs that are used for the replication.  it does use rowguid, so you want those indexes...

Good luck.

I'm not as familiar with merge replication, but you can do the following.  Usually that error message is timeout related (basically something is taking too long, and not reporting...

Try this...

The only thing is that you need to attach to the same server...

exec sp_configure 'allow updates', 1

reconfigure with override

go

update sysdatabases set category=0 where name='your db name here'

go

--detach here

--attach...

It simply looks like you have contention issues.  Transactional or Merge?

What I meant is that its the same thing.  It does really matter how many subscribers you have.  It will be a single Log Reader agent going againt the publisher. ...

Why not use the current publisher to both subscribers?  Just break out the publication to 2 separate ones; one for one subsriber, and one for both subscribers.