one table will not replicate

Did you try a dummy update, ie
set rowcount 5
update tablename set col1=col1

Then use select * From distribution.dbo.msdistribution_status and see if the
undelivered commands increases by 5 for that article id?


"itsonlyme4 via SQLMonster.com" wrote in message
news:85e6aa5b149f5@uwe...
> MS SQL Server 2000 sp4 push publication.....
>
> I am having a real problem getting one article added to an existing
> subscrition. The table exists in both DBs (Publisher and subscriber)
> with
> the proper PK
>
> I've tried every combination I can think of.. reinitialize, snapshot
> etc...
>
> my log reader runs continuously and my REPL distribution agent kicks off
> every 15 minutes.
>
> Can someone please tell me the proper steps to get this one little table
> to
> replicate??
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums...ation/200806/1
>

dummy update on the publishing table? I'm not sure what set col1=col1 does..
This is a production environment...

Hilary Cotter wrote:
>Did you try a dummy update, ie
>set rowcount 5
>update tablename set col1=col1
>
>Then use select * From distribution.dbo.msdistribution_status and see if the
>undelivered commands increases by 5 for that article id?
>
>> MS SQL Server 2000 sp4 push publication.....
>>
>[quoted text clipped - 12 lines]
>> to
>> replicate??

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums...ation/200806/1

itsonlyme4 wrote:
>dummy update on the publishing table? I'm not sure what set col1=col1 does..
>This is a production environment...
>
>>Did you try a dummy update, ie
>>set rowcount 5
>[quoted text clipped - 8 lines]
>>> to
>>> replicate??

These are the results from select * From distribution.dbo.
msdistribution_status
Article_id agent_id UndelivCmdsInDistDB DelivCmdsInDistDB
11 1 13 0
12 1 3 0
14 1 27 0
17 1 18 0
37 1 10 0
38 1 373 0

How do I display the Article_id for each article so I know which one is the
one in question?

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums...ation/200806/1

itsonlyme4 wrote:
>>dummy update on the publishing table? I'm not sure what set col1=col1 does..
>>This is a production environment...
>[quoted text clipped - 4 lines]
>>>> to
>>>> replicate??
>
>These are the results from select * From distribution.dbo.
>msdistribution_status
>Article_id agent_id UndelivCmdsInDistDB DelivCmdsInDistDB
>11 1 13 0
>12 1 3 0
>14 1 27 0
>17 1 18 0
>37 1 10 0
>38 1 373 0
>
>How do I display the Article_id for each article so I know which one is the
>one in question?


I do know that once my REPL distribution agent ran, and I executed select *
From distribution.dbo.
msdistribution_status again, the undeliverable count went to all zeros and I
checked the row counts for the publishing and subscribing tables and there is
a 30 row difference

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums...ation/200806/1

When you update a column to the value it had before it causes data motion,
in other words the log reader will pick up the data. But the column values
will remain the same. So if the value of Col1 was itsonlyme4 before you
would update it to itsonlyme4.

"itsonlyme4 via SQLMonster.com" wrote in message
news:85eabb2eb1207@uwe...
> dummy update on the publishing table? I'm not sure what set col1=col1
> does..
> This is a production environment...
>
> Hilary Cotter wrote:
>>Did you try a dummy update, ie
>>set rowcount 5
>>update tablename set col1=col1
>>
>>Then use select * From distribution.dbo.msdistribution_status and see if
>>the
>>undelivered commands increases by 5 for that article id?
>>
>>> MS SQL Server 2000 sp4 push publication.....
>>>
>>[quoted text clipped - 12 lines]
>>> to
>>> replicate??
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums...ation/200806/1
>

Hilary Cotter wrote:
>When you update a column to the value it had before it causes data motion,
>in other words the log reader will pick up the data. But the column values
>will remain the same. So if the value of Col1 was itsonlyme4 before you
>would update it to itsonlyme4.
>
>> dummy update on the publishing table? I'm not sure what set col1=col1
>> does..
>[quoted text clipped - 13 lines]
>>>> to
>>>> replicate??

I did this and the the undelivered commands did not increase by 5 for that
article id....???

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums...ation/200806/1

There is a condition where the table goes read only. It is normally caused
when you do some dbcc indexing operation against it.

I am not sure how to solve it.

Hilary
"itsonlyme4 via SQLMonster.com" wrote in message
news:85eba01169b73@uwe...
> Hilary Cotter wrote:
>>When you update a column to the value it had before it causes data motion,
>>in other words the log reader will pick up the data. But the column values
>>will remain the same. So if the value of Col1 was itsonlyme4 before you
>>would update it to itsonlyme4.
>>
>>> dummy update on the publishing table? I'm not sure what set col1=col1
>>> does..
>>[quoted text clipped - 13 lines]
>>>>> to
>>>>> replicate??
>
> I did this and the the undelivered commands did not increase by 5 for that
> article id....???
>
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums...ation/200806/1
>