This is actually a post on a non MS forum from my coworker who deals with SQL I'm assisting him on this SQL Replication issue.
Both SQL server 2005 SP4 on Windows 2003. Replication was working untill about a week ago and we tried to rebuild a couple of times but no luck.
"
I have a transactional replication publication with about 30 tables. Most of these tables are being replicated as expected. When I run a trace I can see their sp_MSupd_dboXXXXX
procedures running, I can verify that the data is in sync.
However, for one table, this is not happening. When I looked in the database the table was being replicated to, it did not even
have its own sp_MSins, upd, and del procedures.
When I run sp_browsereplcmds and provide its publication_database_id and article_id, I can see that the command is waiting to be run.
For example, it might say
{CALL sp_MSins_dboTableName (fields here)}. It will sit there for a while, then disappear.
My first assumption was that it wasn't being applied because the procedure didn't exist. So I wrote my own insert proc to confirm this (@c1
datatype, @c2 datatype etc...) and tested it to be sure it worked.
But even then, when I do an insert, the command sits in the repl_commands table for
a while, then disappears, and no row ever hits my table.
I'm getting pretty lost here. Can anyone help? Thanks!
EDIT I should add some more detail:
The distribution DB lives on the subscriber. There are several publications from the same database on the publisher to the same database lon the subscriber (three to be exact, two work fine, one does not).
On two of the publications, a tracer token is processed within about 4 seconds. On the one I'm having trouble with, the tracer token hangs in
limbo indefinitely
"
, Kristofer Olafsson