Is it possible configure replication for inserts and updates, but not
deletes?
Thanks in advance
Yes, it is. You can either set up snapshot replication which will, in
essence, take a copy of the data at that time and put it on the
subscriber, or you can do transactional replication and have the agent
run at a specified time. I'd recommend the former as that way you
don't have to keep data changes as they happen throughout the day (and
as such it'll be much easier/faster to apply the changes at the
subscriber). You'd also have the problem of telling the distribution
agent when to stop with a transactional replication topology.
> Is it possible configure replication for inserts and updates, but not
> deletes?
Yes. When you set up an article in transactional replication, you
specify the commands that are run at the subscriber for each of
insert, update, and delete to replicate the changes for that article.
In order to not replicate deletes, you could no-op the delete command
for that article.
HTH,
Ben
"Ben Thul" <thu...@gmail.com> wrote in message
news:aa48ce24-40f2-4695...@k39g2000yqb.googlegroups.com...
"Ben Thul" <thu...@gmail.com> wrote in message
news:aa48ce24-40f2-4695...@k39g2000yqb.googlegroups.com...
Snapshot replication: http://technet.microsoft.com/en-us/library/ms151847%28SQL.90%29.aspx
For not replicating the delete commands, the relevant doc is for
sp_addarticle: http://technet.microsoft.com/en-us/library/ms173857%28SQL.90%29.aspx,
specifically the @del_cmd parameter.
The docs for 2000 are going to be found in BOL as well (but the SQL
2000 BOL, of course). Good luck!
--
Ben
On Jul 5, 9:46 pm, "RG" <nob...@nowhere.com> wrote:
> Thanks for your help. Could you point me to sample configuration of this.
>
> "Ben Thul" <thul...@gmail.com> wrote in message