Replication problems after SP4 upgrade

Hi,
We're experiencing a problem with transaction replication on SP4.
The snapshot is taken without any problems and applies, however, when it
comes to processing the additional transactions which have taken place since
the snaphot, the process starts processing in parrallel and blocks itself.
The process eventually fails and rollbacks.
This used to work fine on SP3a, but not any more... anyone any ideas?
Thanks in advance
Dave
Dave Wall
what do you mean by processing in parallel? Can you log the output to a text
file and post it here.
Follow these step on how to enable logging.
http://support.microsoft.com/default...b;en-us;312292
Hilary Cotter
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
"Dave Wall" <DaveWall@.discussions.microsoft.com> wrote in message
news:3B4815C4-7438-4C5C-8F81-B9720EB1B0B3@.microsoft.com...
> Hi,
> We're experiencing a problem with transaction replication on SP4.
> The snapshot is taken without any problems and applies, however, when it
> comes to processing the additional transactions which have taken place
since
> the snaphot, the process starts processing in parrallel and blocks itself.
> The process eventually fails and rollbacks.
> This used to work fine on SP3a, but not any more... anyone any ideas?
> Thanks in advance
> Dave
> --
> Dave Wall
|||Hi Dave, it would be great if you can post the [abridged] result of sp_who2
on the distributor\subscriber (or wherever the blocking occurs) as well.
Thanks.
-Raymond
"Dave Wall" wrote:

> Hi,
> We're experiencing a problem with transaction replication on SP4.
> The snapshot is taken without any problems and applies, however, when it
> comes to processing the additional transactions which have taken place since
> the snaphot, the process starts processing in parrallel and blocks itself.
> The process eventually fails and rollbacks.
> This used to work fine on SP3a, but not any more... anyone any ideas?
> Thanks in advance
> Dave
> --
> Dave Wall
|||Hi Raymond,
Got the thing sorted last night. Two things helped. The first was to
increase the minimum query plan threshold for considering paralell execution.
Secondly - we found that our networks team hadn't set the server up with PAE
extensions and so SQL wasn't using all the memory i'd assigned it. Once
these two were changed - replication went through first time.
Looks like a similar problem we had with a another server (see another post)
were processes were blocking themselves. Without the additional memory, IO
went through the roof and the spids started blocking themselves (whilst
waiting for IO)
Sorted the memory, and alls well now.
Thanks
Dave
Dave Wall
"Raymond Mak [MSFT]" wrote:
[vbcol=seagreen]
> Hi Dave, it would be great if you can post the [abridged] result of sp_who2
> on the distributor\subscriber (or wherever the blocking occurs) as well.
> Thanks.
> -Raymond
> "Dave Wall" wrote:
|||Dave,
Am curious which server needed the extra memory. Was it pub, sub, or
dist?
Thanks
Mark Andersen