Receiving 'PRIMARY KEY constraint 'PK__@snapshot_seqnos' error...

I'm adding a new subscriber to a transactional publication (no snapshot) and
I'm receiving a 'Violation of PRIMARY KEY constraint
'PK__@.snapshot_seqnos__543BF21A'. Cannot insert duplicate key in object
'#5253A9A8'.' error. The subscriber, remote distributor and publisher are all
running SP3.
I did some research and it appears this is fixed in MS03-031:
http://support.microsoft.com/default...b;en-us;813494
Can this be installed just on the distributor w/o affecting the other
systems? We actually have 5 other subscribers and some also publish to other
subscribers and also to other publishers so I don't want to affect any of the
other other servers.
TIA!!
Darin
While I can't comment about your individual case, I find that using
different service pack levels/hotfixes across the computers involved in a
replication topology can give unpredictable results. The recommended upgrade
path does start with the distributor, then publisher then subscriber, but in
your case I'd apply sp4 to all computers (in this order but in one shot)
rather than one by one and running replication inbetween.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Have a look at this post.
http://groups.google.com/group/micro...0?dmode=source
This will fix it. IIRC you will make this change on the distributor.
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
"DTully" <DTully@.discussions.microsoft.com> wrote in message
news:45B780CE-96CF-45AE-8716-BE22A062C5FE@.microsoft.com...
> I'm adding a new subscriber to a transactional publication (no snapshot)
> and
> I'm receiving a 'Violation of PRIMARY KEY constraint
> 'PK__@.snapshot_seqnos__543BF21A'. Cannot insert duplicate key in object
> '#5253A9A8'.' error. The subscriber, remote distributor and publisher are
> all
> running SP3.
> I did some research and it appears this is fixed in MS03-031:
> http://support.microsoft.com/default...b;en-us;813494
> Can this be installed just on the distributor w/o affecting the other
> systems? We actually have 5 other subscribers and some also publish to
> other
> subscribers and also to other publishers so I don't want to affect any of
> the
> other other servers.
> TIA!!
> Darin

Rebuild indexes on subscriber?

In a transactional replication scenario, should i consider rebuilding
indexes on the subscriber articles? Does that place a lock on the
subscriber? most of those tables are used only for select queries.
Thanks.
IN SQL 2000 is does, with online=on in SQL 2005 EE it does not.
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
"rt" <rtemple3@.gmail.com> wrote in message
news:1171914789.341188.155130@.l53g2000cwa.googlegr oups.com...
> In a transactional replication scenario, should i consider rebuilding
> indexes on the subscriber articles? Does that place a lock on the
> subscriber? most of those tables are used only for select queries.
> Thanks.
>
|||Just to add to Hilary's anwser, you could use dbcc indexdefrag if concerned
about table locks required when using dbcc dbreindex for SQL Server 2000. In
SQL Server 2005, as well as the Alter Index versions of these DBCC
statements, there is the posibility of using READ_COMMITTED_SNAPSHOT
isolation in the client queries.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Rebuild and Reorganize

will maintenance tasks like rebuilding and reorganizing indexes be replicated in transactional replication, or do i have to setup these management tasks on the subscribers as well?

No. These operations are not replicated.

Peng

|||so if i set these tasks up on the subscriber will it affect replication in a negative way?|||As far as I know, there should be no negative impact. Of course, you need to test on your machines to see if the extra workload affects the performance much.