Reinitializing a subscription

Win 2000 & SQL 2000 SP3
I have a publication that wants to be reinitialized (The
subscription(s) have been marked inactive and must be reinitialized.
NoSync subscriptions will need to be dropped and recreated.). When I
created the push subscription, I did it NoSync, so I know I have to
drop and recreate it. But, my question is this....How can I prevent
from loosing the transactions that are pending? If I drop the
subscription & recreate it, the pending transactions will be
lost...right?!?!? I need these. HELP
TIA,
Larry...
Yes you are correct. The best approach to this sort of problem is to use
sp_browsereplcmds like this
sp_browsereplcmds @.publisher_database_id = 7,@.results_table =
'results_table'
where @.publisher_database_id is your publication database ID.
Then you have the commands stored in your results table. You can run these
on your subscriber. You can also use @.xact_seqno_start to define a start id.
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
<lreames@.gmail.com> wrote in message
news:1112196237.338064.299320@.o13g2000cwo.googlegr oups.com...
> Win 2000 & SQL 2000 SP3
> I have a publication that wants to be reinitialized (The
> subscription(s) have been marked inactive and must be reinitialized.
> NoSync subscriptions will need to be dropped and recreated.). When I
> created the push subscription, I did it NoSync, so I know I have to
> drop and recreate it. But, my question is this....How can I prevent
> from loosing the transactions that are pending? If I drop the
> subscription & recreate it, the pending transactions will be
> lost...right?!?!? I need these. HELP
> TIA,
> Larry...
>

reinitialized subscription

Running - Win 2K / SQL 2K
I am constantly getting an error on a merge
publication/subscription that I have...
The subscription(s) have been marked inactive and must be
reinitialized. NoSync subscriptions will need to be
dropped and recreated.
How can I prevent this from happening?
What is causing this?
Larry...
you normally get this error when your subscribers haven't connected to your
publisher within 14 days for transactional and merge publications.
The way to prevent this is to ensure your subscriber connects to your
publisher within this period.
Exactly how frequently are you getting this error?
"larry" <anonymous@.discussions.microsoft.com> wrote in message
news:89a401c432b4$81e001e0$a401280a@.phx.gbl...
> Running - Win 2K / SQL 2K
> I am constantly getting an error on a merge
> publication/subscription that I have...
> The subscription(s) have been marked inactive and must be
> reinitialized. NoSync subscriptions will need to be
> dropped and recreated.
> How can I prevent this from happening?
> What is causing this?
> Larry...
|||.....Exactly how frequently are you getting this error?
Hilary,
I get this on one of my continous transactional
subscriptions once every couple of weeks. I check
replication every day and in fact, the SQL server agent
gets restarted every night @. 2:00 am.
Larry...

Reinitialize subscriptions in transactional replication

If I have one table in one publication in transactional replication
replication between primary and replicate is broken because subscription is marked as inactive.

If there are 3 rows on replicate and 5 rows on primary , out of which 2 are added after replication is broken

If I do

Reinitialize subscriptions
start the snapshot agent
start the distribution agent

Does this mean that it will only transfer the new 2 rows to replicate sites ? or will it drop everything from replicate site and apply all rows from primary site on to replicate.

Any help is appreciatedIt will drop every article the subscriber subscribes and refresh the DDL and data from the publication.