sql server replication: Merge replication and history -- sql server replication

Merge replication and history

andsm
9/6/2003 11:30:49 PM

sql server replication:

I have two tables, one table, table A, with actual
information, table B with history information. table B have
same structure as table A, except it have have two more
fields. Each time when a record in table A inserted, deleted
or updated, the record is copyed to table B, with additional
information. Table B have no references to table A, to allow
deletes from table A.
MSSQL2k EE. I need replicate the data, with merge
replication, between servers, all servers is MSSQL2k EE.
The problem, as I see it, in case of conflict new update from
table A would be discarded, but record to table B would be
added - about update which was discarded. How it is

Re: Merge replication and history

Wayne Snyder
9/8/2003 5:35:26 AM

You simply need to publish both A and B..

Any foreign key problems you have with your design are not related to the
replication issue... If you need, you might add a key in B that points to A,
so you can cascade deletes etc...

--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)

I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org

[quoted text, click to view]