Groups | Blog | Home
all groups > sql server replication > may 2005 >

sql server replication : Deleting and meta-data


Rob Blij
5/20/2005 12:00:00 AM
Is there a way to delete from a table but not send any meta-data into
msmerge_tombstone?

I have readonly data which I delete every morning and have an integration
run which brings me my new data. Problem is this creates TONS of meta data
which is totally unnessary.

tia
Rob

Paul Ibison
5/20/2005 12:00:00 AM
Rob,
you could disable the merge delete trigger (ALTER TABLE DISABLE TRIGGER
name) before the delete and reenable afterwards.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Rob Blij
5/20/2005 12:00:00 AM
What effect would this have on having to delete the meta data every morning.
If we disable the trigger then delete all the data and insert new data,
wouldnt the publication get confused when the subscribers now have to sync?

tnx

[quoted text, click to view]

Paul Ibison
5/20/2005 12:00:00 AM
In this case, just the new data would be synchronized. There would however
be issues if the publisher deletes/updates the records that you have removed
outside of replication on the subscriber. Also you won't be able to run
validations. This all assumes from your original description that you don't
want these deletes to be replicated to the publisher - let's just confirm
that this is correct? If you are trying to have all records amalgamated at
the publisher but only a subset at the subscriber, you could use filters, in
which case inserts on the subscriber will be sent to the publisher on
synchronization and replicated back as deletes to the subscriber. This way
uses the existing replication setup.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)



AddThis Social Bookmark Button