Re: Distribution Data File Growth
- From: "michelle" <michelle@xxxxxxxxxx>
- Date: Thu, 14 Apr 2005 15:40:43 -0500
Thanks. I had all of the pieces (msdb, distribution, master, etc.). All
databases were restored but since I didn't back up the publishers with the
keep_replication switch, I couldn't get replication 'kicked off' again. I
re-marked them after the restore for replication and all of the jobs were
succeeding. However, the log reader was not finding any transactions.
No open transactions in distribution. I'll see where Paul's suggestion leads
me...
"Hilary Cotter" <hilary.cotter@xxxxxxxxx> wrote in message
news:1113509425.813891.157720@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> run a dbcc opentran in your distributon database to see what happens.
>
> The keep replication switch was designed to be enable disaster recovery
> of your transactional replication solution. You can use it to restore
> publications on a server but only so you can script out the
> publications or view them. Don't expect to use the keep_replication
> swithc on a new server and have everything work. You need to restore
> the distribution, master, and msdb databases as well.
>
.
- References:
- Distribution Data File Growth
- From: michelle
- Re: Distribution Data File Growth
- From: Hilary Cotter
- Distribution Data File Growth
- Prev by Date: Re: Distribution Data File Growth
- Next by Date: Re: Distribution Data File Growth
- Previous by thread: Re: Distribution Data File Growth
- Next by thread: Log Shipping: how to avoid connection resets on secondary
- Index(es):
Relevant Pages
|