"Greg Simpson" <Greg.Simpson@myflorida.com> wrote in message
news:0a5601c3cfcb$53e6ef20$a601280a@phx.gbl...
> HELP!
>
> I have just taken over mgmt of a SQL Server warehouse
> architecture that uses replication to propogate changes
> from a staging server to a production server. The
> replication has been broken since 04 Dec. When attempting
> to reinitialize the subscription, SQL tells me that I must
> drop and recreate the subscription. The 2 DBs are not that
> much out of synch, so I don't want to do a full resynch
> with bulk copy if it can be avoided (they are huge).
> However, when I recreate the subscription with "generate
> scripts and copy data" radio button OFF, I get the
> following error:
>
> Violation of PRIMARY KEY
> constraint 'PK__@snapshot_seqnos__39924EC9'.
> Cannot insert duplicate key in object '#389E2A90'.
>
> I've researched and determined that the constraint in
> question is against a temp table declared in the
> replication SPs which run to begin the reinit process.
> I've searched the MS knowledgebase with no significant
> hits. The server is up to date on maint.
>
> Any help with this would be much appreciated!!!
>
> Greg Simpson

"Greg Simpson" <Greg.Simpson@myflorida.com> wrote in message
news:0a5601c3cfcb$53e6ef20$a601280a@phx.gbl...
> HELP!
>
> I have just taken over mgmt of a SQL Server warehouse
> architecture that uses replication to propogate changes
> from a staging server to a production server. The
> replication has been broken since 04 Dec. When attempting
> to reinitialize the subscription, SQL tells me that I must
> drop and recreate the subscription. The 2 DBs are not that
> much out of synch, so I don't want to do a full resynch
> with bulk copy if it can be avoided (they are huge).
> However, when I recreate the subscription with "generate
> scripts and copy data" radio button OFF, I get the
> following error:
>
> Violation of PRIMARY KEY
> constraint 'PK__@snapshot_seqnos__39924EC9'.
> Cannot insert duplicate key in object '#389E2A90'.
>
> I've researched and determined that the constraint in
> question is against a temp table declared in the
> replication SPs which run to begin the reinit process.
> I've searched the MS knowledgebase with no significant
> hits. The server is up to date on maint.
>
> Any help with this would be much appreciated!!!
>
> Greg Simpson

>-----Original Message-----
>reboot your sever. Drop the subscriptions and then do a
resync with the
>option the subscriber already has the schema and data.
>
>I would also try to do some binary checksum analysis
against your tables to
>see which rows if any are out of sync.
>
>"Greg Simpson" <Greg.Simpson@myflorida.com> wrote in
message
>news:0a5601c3cfcb$53e6ef20$a601280a@phx.gbl...
>> HELP!
>>
>> I have just taken over mgmt of a SQL Server warehouse
>> architecture that uses replication to propogate changes
>> from a staging server to a production server. The
>> replication has been broken since 04 Dec. When
attempting
>> to reinitialize the subscription, SQL tells me that I
must
>> drop and recreate the subscription. The 2 DBs are not
that
>> much out of synch, so I don't want to do a full resynch
>> with bulk copy if it can be avoided (they are huge).
>> However, when I recreate the subscription with "generate
>> scripts and copy data" radio button OFF, I get the
>> following error:
>>
>> Violation of PRIMARY KEY
>> constraint 'PK__@snapshot_seqnos__39924EC9'.
>> Cannot insert duplicate key in object '#389E2A90'.
>>
>> I've researched and determined that the constraint in
>> question is against a temp table declared in the
>> replication SPs which run to begin the reinit process.
>> I've searched the MS knowledgebase with no significant
>> hits. The server is up to date on maint.
>>
>> Any help with this would be much appreciated!!!
>>
>> Greg Simpson
>
>
>.