Multi publisher single subscrier Replication

I had a multi publisher single subscriber replication in my job and now i want remove it. i disabled the subscriber. Now if i disable the publisher and distributor then it gives me a error cannot drop the distribution DB because it is currently in use. this DB can never be dropped since there is at least one publisher at one time that accesses this DB everytime. How should I disable this publication.

Disable each Publisher, removing any publications caused by that Publisher. Leave the Distribution database until you are removing the final Publisher and then it 'should' be removable.

sql

msSQL2000 to mssql2005

I have set up a replication between mssql2000 to mssql2005
Mssql2000 is the publisher and mssql is subscriber.
And it work fine.
Then I remove the publication because I need to do spm Alter statement
against Tables in the database
When I try to add subscription
with @.sync_type = N'none' (In This case the data i alredy in the subscribers
databse)
I get theese error:
Violation of PRIMARY KEY constraint 'PK__@.snapshot_seqnos__328568A3'.
Cannot insert duplicate key in object '#3191446A'.
(Source: SRVIQDB03 (Data source); Error number: 2627)
Her is Add subscr.
use [Tellus_DB209]
exec sp_addsubscription @.publication = N'pub_Tellus_DB209_2005',
@.subscriber = N'RDASP21', @.destination_db = N'Tellus',
@.subscription_type = N'Push', @.sync_type = N'none',
@.article = N'all', @.update_mode = N'read only',
@.loopback_detection = N'True',
@.frequency_type = 64, @.frequency_interval = 0, @.frequency_relative_interval
= 0,
@.frequency_recurrence_factor = 0, @.frequency_subday = 0,
@.frequency_subday_interval = 0,
@.active_start_time_of_day = 0, @.active_end_time_of_day = 235959,
@.active_start_date = 20060202, @.active_end_date = 99991231, @.offloadagent =
0,
@.enabled_for_syncmgr = N'False', @.dts_package_location = N'Distributor'
What is this about.
What sp is SQL 2000? You may need to check this link to fix the problem.
http://groups.google.com/group/micro...5?dmode=source
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
"Roger Nygrd" <roger@.askit.no> wrote in message
news:11u4op7pil83qf4@.corp.supernews.com...
>I have set up a replication between mssql2000 to mssql2005
> Mssql2000 is the publisher and mssql is subscriber.
> And it work fine.
> Then I remove the publication because I need to do spm Alter statement
> against Tables in the database
> When I try to add subscription
> with @.sync_type = N'none' (In This case the data i alredy in the
> subscribers databse)
> I get theese error:
> Violation of PRIMARY KEY constraint 'PK__@.snapshot_seqnos__328568A3'.
> Cannot insert duplicate key in object '#3191446A'.
> (Source: SRVIQDB03 (Data source); Error number: 2627)
> Her is Add subscr.
> use [Tellus_DB209]
> exec sp_addsubscription @.publication = N'pub_Tellus_DB209_2005',
> @.subscriber = N'RDASP21', @.destination_db = N'Tellus',
> @.subscription_type = N'Push', @.sync_type = N'none',
> @.article = N'all', @.update_mode = N'read only',
> @.loopback_detection = N'True',
> @.frequency_type = 64, @.frequency_interval = 0,
> @.frequency_relative_interval = 0,
> @.frequency_recurrence_factor = 0, @.frequency_subday = 0,
> @.frequency_subday_interval = 0,
> @.active_start_time_of_day = 0, @.active_end_time_of_day = 235959,
> @.active_start_date = 20060202, @.active_end_date = 99991231, @.offloadagent
> = 0,
> @.enabled_for_syncmgr = N'False', @.dts_package_location = N'Distributor'
> What is this about.
>

MSSQL_ENG020598 - The row was not found at the Subscriber when applying the replicated command.

Hello,

We are seeing error MSSQL_ENG020598 - "The row was not found at the Subscriber when applying the replicated command", when running peer to peer transactional replication. Unfortunately the error message provides the database in which the error occurs but not the table or SQL statement that causes the conflict.

Is there a way to determine exactly what query caused the conflict - or at least what table the error occurred in?

Thanks in advance.

If you run distribution agent in a job, you can set the OutputVerboseLevel of distribution agent profile to 2.

If you run distribution agent from command line, simply set parameter -OutputVerbloseLevel to 2.

It shows the exact SQL statement that distribution agent use.

Peng

|||Thanks, this looks like it helped.

MSSQL Replication (Type Merge)

Hello, i have this 2 errors. Pleas for help.
The process could not check existence of generation at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147201003)
General network error. Check your network documentation.
(Source: SERWER (Data source); Error number: 11)
Access to internet is ok.
On Firewall all is allow.
Greeting Huryn Adrian.
You are having one of two issues.
1. Network connectivity
2. You are having blocking issues within the merge metadata tables which
means you are probably carrying around too much tracking information.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Adrian Huryn" <ahuryn@.ist.net.pl> wrote in message
news:20060210100829.af82c9a0.ahuryn@.ist.net.pl...
> Hello, i have this 2 errors. Pleas for help.
> The process could not check existence of generation at the 'Subscriber'.
> (Source: Merge Replication Provider (Agent); Error number: -2147201003)
> General network error. Check your network documentation.
> (Source: SERWER (Data source); Error number: 11)
> Access to internet is ok.
> On Firewall all is allow.
> Greeting Huryn Adrian.
|||On Fri, 10 Feb 2006 12:43:22 -0600
"Michael Hotek" <mike@.solidqualitylearning.com> wrote:

> You are having one of two issues.
> 1. Network connectivity
I have this check, pings/tracerouts are good. On bouth sites all work fine.

> 2. You are having blocking issues within the merge metadata tables which
> means you are probably carrying around too much tracking information.
What i can make here ?
Greeting, Huryn Adrian.
|||You need to validate that you get make a connect from your Subscriber to your
Publisher. If you can make a SQL connection then look at adjusting the
Subscriber Merge Agent Profile to a Slow Link Profile because this your
subscriber might have a slow connection and you need to lengthen the timeout
settings.
The blocking issues and/or large number of records in the merge replication
tables. I have used the following process successfully but I have one
replication which makes this process easier to implement.
Look up in BOL: sp_mergecleanupmetadata
"Adrian Huryn" wrote:

> On Fri, 10 Feb 2006 12:43:22 -0600
> "Michael Hotek" <mike@.solidqualitylearning.com> wrote:
> I have this check, pings/tracerouts are good. On bouth sites all work fine.
> What i can make here ?
> Greeting, Huryn Adrian.
>