Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
 Posted - 2002-05-02 : 09:40:35
|
| Here's a real guru question for you all:I have a table being replicated transactionally from server a to b. I can verify through Profiler that when an update is issued against the table, the agent does not call the sp_MSupd* stored procedure on server b, but rather splits the update into two calls to sp_MSdel* and sp_MSins*. There's nothing custom about the replication setup - it's not a transformable subscription, none of the replication stored procedures are custom, etc. It's a plain vanilla transactional replication.While this is usually an equivalent operation, there are triggers on the server b table for reporting purposes, and they require the differentiation of an update being performed as opposed to a delete followed by an insert. In particular having two sp's being called for one update makes it very difficult to persist any information across the two calls.Any ideas?setBasedIsTheTruepath<O> |
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2002-05-02 : 10:21:23
|
| never mind all, i finally found it:[url]http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q302341[/url]setBasedIsTheTruepath<O> |
 |
|
|
|
|
|
Root cause of replication splitting updates?