Subscriptions Reinitialize with No Explanation in Transaction Replication -- sql server replication

joao NO[at]SPAM braviawebdesign.com
10/20/2006 12:42:30 PM

Here is my topolgy: I have one server acting as both publisher and
distributor. The publisher has a one way transactional publication.
This publication has two articles with blob columns, one is ntext and
the other is an image (ItemDescriptions and ItemImages, respectively).
Everytime I make a lot of inserts to those two tables at once (maybe
two hundred rows in each table), the subscriber goes into performance
critical mode, with a latency of maybe 15 minutes. And after that I get
the message that the initial snapshot is not yet available for the
publication. Even though a quick row count tells me that all the rows
have in fact been replicated. This has happened several times now. I
know for a fact that the data is synchronized (No changes have been
made to the articles). What could be causing this problem? And if I
can't fix it, can I work around it? Is there any way I can force the
subscription to reactive without reapplying the snapshot? This is in
production and doing so would take several hours.

Hilary Cotter
10/20/2006 5:03:50 PM

There is something wrong here. expect text and image data to take a long
time to replicate but it should not expire the subscription. What version of
SQL Server are you running and what sp?

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com

[quoted text, click to view]

sql server replication : Subscriptions Reinitialize with No Explanation in Transaction Replication