Replication Monitor

experiencing some very odd behavior in Enterprise Manager.
I have a process that performs the following:
1.) Restores a published database from Server A onto Server B. The
databases
are identical and they are both published.
2.) I run a script that then deletes the subscriptions to the
publication on
Server B. I do this via SP_DROPSUBSCRIPTION.
3.) I run a script that then deletes the publication. I do this via
SP_DROPPUBLICATION.
4.) Deletes the distribution database.
5.) Deletes the old jobs.
6.) Creates the publication from pregenerated scripts.
7.) Adds the subscriber.
8.) Adds the subscription.
9.) Generates the snapshot and applies it.
What's happening is that I'm seeing the job name that's assigned to the
distribution job increment by 1 each time this process is run. Also,
I'm seeing ten instances of the publication showing up in the tree view.
When I look in SYSPUBLICATIONS, there is only ONE row!!! Shouldn't
Replication Monitor clean itself up?
Everything appears to be rtunning just fine, transactions being
replicated, etc. I'm just wondering is there something I'm missing in my
steps.
Plus, after two or three months of this, might not look so good having 90
publications showing up in the tree view.
Thanks!
first off run a sp_MSload_replication_status. This can occasionally correct
these problems. Secondly, it looks like your replication metadata is messed
up. It is normal for the publications to increment their names with every
new publication. However, to determine how to fix your error I need to know
which node you are getting the error in?
The Publication node in the replication folder? The Publishers node in the
Replication Monitor folder?
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
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:FE4B9FD8-5948-45AF-A3F8-8F9867CFBC23@.microsoft.com...
> experiencing some very odd behavior in Enterprise Manager.
>
> I have a process that performs the following:
>
> 1.) Restores a published database from Server A onto Server B. The
> databases
> are identical and they are both published.
> 2.) I run a script that then deletes the subscriptions to the
> publication on
> Server B. I do this via SP_DROPSUBSCRIPTION.
> 3.) I run a script that then deletes the publication. I do this via
> SP_DROPPUBLICATION.
> 4.) Deletes the distribution database.
> 5.) Deletes the old jobs.
> 6.) Creates the publication from pregenerated scripts.
> 7.) Adds the subscriber.
> 8.) Adds the subscription.
> 9.) Generates the snapshot and applies it.
>
> What's happening is that I'm seeing the job name that's assigned to the
> distribution job increment by 1 each time this process is run. Also,
> I'm seeing ten instances of the publication showing up in the tree view.
> When I look in SYSPUBLICATIONS, there is only ONE row!!! Shouldn't
> Replication Monitor clean itself up?
> Everything appears to be rtunning just fine, transactions being
> replicated, etc. I'm just wondering is there something I'm missing in my
> steps.
> Plus, after two or three months of this, might not look so good having 90
> publications showing up in the tree view.
>
> Thanks!
>
>
|||Hilary:
I'm seeing this in the publishers node under Replication Monitor...
When would I run the sp_MSload_Replication_Status? I just ran it and it
killed my replication. I'm guessing you don't want to run that proc after
replication has been established...
Thanks!
"Hilary Cotter" wrote:

> first off run a sp_MSload_replication_status. This can occasionally correct
> these problems. Secondly, it looks like your replication metadata is messed
> up. It is normal for the publications to increment their names with every
> new publication. However, to determine how to fix your error I need to know
> which node you are getting the error in?
> The Publication node in the replication folder? The Publishers node in the
> Replication Monitor folder?
> --
> 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
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:FE4B9FD8-5948-45AF-A3F8-8F9867CFBC23@.microsoft.com...
>
>
|||What do you mean by it "killed" off replication? I should fix transient
errors. Are you saying that some agents are no longer showing up in the
snapshot/distribution/log reader agent folders?
If so, I think this is caused by scripting out replication and running the
same script in a different database without modifying the snapshot, log
reader, or distribution agent names, and without modifying the publication
name. I think you will find that the agents just don't show up, but
everything works fine.
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
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:B69FA4F3-EFA7-40B2-A709-9B08335CE455@.microsoft.com...[vbcol=seagreen]
> Hilary:
> I'm seeing this in the publishers node under Replication Monitor...
> When would I run the sp_MSload_Replication_Status? I just ran it and it
> killed my replication. I'm guessing you don't want to run that proc after
> replication has been established...
> Thanks!
> "Hilary Cotter" wrote:
correct[vbcol=seagreen]
messed[vbcol=seagreen]
every[vbcol=seagreen]
know[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
view.[vbcol=seagreen]
my[vbcol=seagreen]
90[vbcol=seagreen]
|||I stand corrected...everything came back.
But I'm still seeing the multiple publications under the publishers tab of
the replication monitor...
"Hilary Cotter" wrote:

> What do you mean by it "killed" off replication? I should fix transient
> errors. Are you saying that some agents are no longer showing up in the
> snapshot/distribution/log reader agent folders?
> If so, I think this is caused by scripting out replication and running the
> same script in a different database without modifying the snapshot, log
> reader, or distribution agent names, and without modifying the publication
> name. I think you will find that the agents just don't show up, but
> everything works fine.
> --
> 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
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:B69FA4F3-EFA7-40B2-A709-9B08335CE455@.microsoft.com...
> correct
> messed
> every
> know
> the
> the
> view.
> my
> 90
>
>
|||...also, the scripts that are being used to recreate the replication topology
were generated on the Server B - so the agent names, databases, subscription
names are all correct for that particular server...
"A. Robinson" wrote:
[vbcol=seagreen]
> I stand corrected...everything came back.
> But I'm still seeing the multiple publications under the publishers tab of
> the replication monitor...
> "Hilary Cotter" wrote: