Replication Screwup

Running SQL 2005 on Win 2003....
First, I cannot find sp_MSload_replication_status. When I run it, I
get the following error
Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'sp_MSload_replication_status'.
Is the SP not a part of 2005?
Second... I attempted to remove publications & push subscriptions,
from the publisher, via a script, see below...
DECLARE @.subscriptionDB AS sysname
SET @.subscriptionDB = N'EDI'
-- Remove replication objects from a subscription database (if
necessary).
USE master
EXEC sp_removedbreplication @.subscriptionDB
GO
This removed the Publication & Subscriptions from SMS, but Replicaiton
Manager still shows them. I have tried numerous scripts with no luck.
How do I clean up replication manger? I tought
sp_removedbreplication removed everything.
AHIA,
Larry...
I have deleted all jobs that reference this database and run
sp_removedbreplication 'EDI'
sp_replicationdboption 'edi','publish','False'
The subscriptions still exist in the replication monitor with the
message...
The concurrent snapshot for publication 'EDI to 04' is not available
because it has not been fully generated or the Log Reader Agent is not
running to activate it. If generation of the concurrent snapshot was
interrupted, the Snapshot Agent for the public
HELP!!!!
|||Did you check the logreader and snapshot jobs on the distribution server?
It could be the snapshot job is still enabled and trying to run.
-Chuck
On 3 May 2007 11:13:58 -0700, LPR-3rd wrote:

> I have deleted all jobs that reference this database and run
> sp_removedbreplication 'EDI'
> sp_replicationdboption 'edi','publish','False'
> The subscriptions still exist in the replication monitor with the
> message...
> The concurrent snapshot for publication 'EDI to 04' is not available
> because it has not been fully generated or the Log Reader Agent is not
> running to activate it. If generation of the concurrent snapshot was
> interrupted, the Snapshot Agent for the public
>
> HELP!!!!
|||sql 2000 only.
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1178211126.029986.247150@.y80g2000hsf.googlegr oups.com...
> Running SQL 2005 on Win 2003....
> First, I cannot find sp_MSload_replication_status. When I run it, I
> get the following error
> Msg 2812, Level 16, State 62, Line 1
> Could not find stored procedure 'sp_MSload_replication_status'.
> Is the SP not a part of 2005?
>
> Second... I attempted to remove publications & push subscriptions,
> from the publisher, via a script, see below...
> DECLARE @.subscriptionDB AS sysname
> SET @.subscriptionDB = N'EDI'
> -- Remove replication objects from a subscription database (if
> necessary).
> USE master
> EXEC sp_removedbreplication @.subscriptionDB
> GO
> This removed the Publication & Subscriptions from SMS, but Replicaiton
> Manager still shows them. I have tried numerous scripts with no luck.
> How do I clean up replication manger? I tought
> sp_removedbreplication removed everything.
> AHIA,
> Larry...
>
|||I had this issue after recoving a crashed database. on server 2005
Dropping / recreating the publications and subscriptions didn't do the trick.
I had to "Disable Replication" , causing all replication related data to be
dropped from the server.
Then I just went through the "Disrtibution" wizard, connected to a
publisher, recreated the pubs and subs and all was well. Didn't have to
rename or do anything else with the source database.

Replication Performance?

I'm having a tough time finding any good resources on Sql Server Replication Performance. Are there any benchmarks / state of any kind? How well does replication scale out?

In my scenario, I have one central publisher and several large tables, all with hundreds of millions of records. Every day I may insert/update millions of records in the publisher, and then I need to replicate the changes (in a few hours at most) onto a pool of subscribers, while they remain online.

Is the replication story robust enough to handle a situation like this?

Is this merge or transactional replication, and on what version lf sql server? And what is the approximate transaction size (meaning how many commands per txn)? Assuming this is transactional replication, performance will depend on your hardware, network bandwidth, size of changes (in K or MB), # of indexes at the subscriber, type of changes (ins, upd or del), existance of triggers, etc.

Throughput of several thousand commands per second is not out of the question, but as I mentioned above, it depends on the above. Tell us more about your scenario and we can comment further. You can reference this basic performance guide, http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx.