Replication

[shuaib]

In transactional replication Can a Publisher also be a subscriber?

[rmiao]

Replicate to db on same server? Yes.

[shuaib]

Replication will be to different servers

How about using Transactional replication with updatable subscriptions.

Any disadvantages?

[skhanal]

Not for the same publication. If you create a separate publication for different set of rows (or columns) it should be possible.

With updatable subscription the network/database must be available for a transaction to commit (unless you use a queued updatable subscription).

With updatable subscription the chances of getting conflicts rises.

[shuaib]

Has this been tried and tested?

Does it actually work.

[rmiao]

It works for me, but you need very reliable network and servers.

[shuaib]

Great.

When it was mentioned 'not for the same publication' could someone expand on that.

Is their any docs/papers that show how to set up updatable subscriptions with transactional replication.

[rmiao]

You can find it in sql books online. For 'not for the same publication', I guess it try to say that you can define publications with filter on multiple servers. Something like you replicate column 1 to 5 of the table from server a to server b, and replicate column 6 to 10 of same table from server b to server a.

[shuaib]

OK.

Can msde be used as a subscriber with updatable subscriptions allowing concurrent connections.

[rmiao]

Yes.