Showing posts with label win. Show all posts
Showing posts with label win. Show all posts

Tuesday, March 20, 2012

replacate Inserts only

Running Win 2k & SQL 2k
How do I create or modify an already created publication
to only replacate Inserts?
Larry,
assuming you are using transactional replication, usually the way to
accomplish this is to change the command called to NONE on the article
properties. However this will force reinitialization of existing
subscriptions. In order to avoid reinitialization, you could modify the
stored procedure called - comment out the code in the update and delete
stored procedures.
HTH,
Paul Ibison
|||So, if the publications have not been created, I can
create them and change the command called to NONE on the
article properties for the delete and update, and this
should work...RIGHT?
Thanks,
Larry...
|||Larry - that's right
Paul
|||thanks, you da man!!!

Repl Mgr reporting error

Win 2k & SQL 2k
I have trans & merge replication between several remote
sites and my main office. On a couple of the Replication
Managers, an error is being reported on a publication.
When I expand the dist agent & the publication folder to
the actual publication, there is no error. I have
restarted the remote server and still the error exists,
even after I refresh the Replication Manager in EM.
Any one have an idea?
Larry,
when I have seen these rogue errors reported before, it was because of
incorrect data in tempdb so restarting the sql server service on the
distributor removed both the erroneous table and the red icon. hilary
mentions that running sp_MSload_replication_status normally clears this
error as well.
HTH,
Paul Ibison
|||I have restarted the server where the publications exist
and they are their own distributors. I ran
sp_MSload_replication_status on both the publisher and
the subscriber and the errors were not cleared. Any
ideas?
|||Larry,
can you try restarting the sql server service on the server which has
replication manager.
If this still doesn't fix it, try using profiler after you refresh the
replication manager and see if you can track it down.
HTH,
Paul Ibison