Updateable subscription 2PC Problems
-
Hello - I have an immediately updatable transactional replication set up between two SQL Servers within a LAN. If I make a change to the server/publisher, I see the change show up within a few seconds on the client/subscriber. However, if I make a change to the client/subscriber that change never occurs at the server/publisher. I get no errors, no log messages (if I'm looking in the right place - though I've looked in both SQL logs and event logs) and change on the client/subscriber is never rolled back. DTC if running on both machines. All the update, insert and delete triggers are in place. Unique GUIDs are assigned to all rows and subscription properties show the database as updatable. Any thoughts on why I seem to be able make local changes in seeming violation of a 2 phase commit? Any good diagnostic practices for this situation?
Thanx!
-
Hello again! As I haven't heard any thoughts on my problem yet, I figure I'd sweeten the pot with a few more clues: Since my last posting I can say that the problem is not in my COM+ subsystem (something I started to suspect but eliminated). The interesting clue however is that even if I shut off my publisher, I can still update rows on my subscriber. There's no delay as if the subscriber is looking for a publisher, no complaints - nothing! The value in the subscriber table gets updated as if the two phase commit worked (or didn't happen in the first place). sp_helpsubscription_properties shows this as an UPDATABLE transactional subscription. I've run sp_link_publisher also but to no avail. Why can't I update my publisher??? HELP!!
-
can you post the content on the insert trigger in the subscriber table?
* Noel
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply