SQL Server replication

Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Joe Black replied

14 February 2007, 20:15
That's what I thought PRC. So I've gone with a design based on that.

Hopefully the DBA will confirm this tomorrow, otherwise I'll have to set up a couple of VMs and find out that way.
Leave a comment:
PRC1964 replied

14 February 2007, 14:38
I can't see why not. Just remove that one table from the Transactional publication and create a new Merge publication.
Leave a comment:
Joe Black started a topic SQL Server replication

14 February 2007, 10:47
SQL Server replication

We have some databases here which get replicated from the intranet to internet side of things. I would like to have one table though which can be updated on the internet end and it's records merged back.

Anyone know if this is possible, having two publications - transactional and merge - on the same database, as our DBA doesn't know and won't have time to test it until tomorrow.

Unfortunately I really need to know today in order to develop a design.
Tags: None