Replication issues

Hi All ,
I have some concerns with replication
1. if the replication fails 1/2 way , does that mean some data is being
replicated across alrdy or it'll do a roll-back to ensure either it's a
complete replication or no replication ?
2. previously i have already set up the application but in EM , i went to
Replication --> Publications and delete the publication instead of going to
the Replication Monitor --> Publishers --> to delete the publication and
found that i couldn't delete the publication in Replication Monitor -->
Publishers any more
which sp can i used to delete ?
3. i got the error from replication "the subscription has been marked and
must be reintialized . No Sync subscriptions will need to be dropped and
recreated?
- why this error occured , i have set for replication for 72 hours
Kindly advise
tks & rdgs
1) this depends. If there is a problem deploying the snapshot, it will be
reapplied, but not rolled back. So if you don't reapply the snapshot after
failure your subscriber database will have some of the replicated objects
and replication metadata in place. If the merge or distribution agent fails
midway it depends on the transactional boundary. Transactional replication
replicates transactions transactionally. So if a transaction with 200
commands (for instance a transaction which updates 200 rows) fails, it will
be completely rolled back. If you are replicating a transaction which causes
a cascading update/delete on the publisher and you have enforced this
cascade for replication, and this transaction fails, it will be rolled back.
For merge replication, if a child record is applied before the corresponding
parent record and the parent is not part of the batch, the agent will fail
and this row will be rolled back, but the successfully applied rows in the
batch will remain. Next time you run the merge agent, this transaction
should succeed if the parent record comes over in the next batch. Merge
replication does not guarantee durability.
2) try sp_droppublication 'publicationname' in the publication database.
3) You should set your history retention to the same value of your
transaction retention (right click on replication monitor, select
distribution properties, and click on the properties button, and set it
there).
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
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:6A1D3EAE-EE3A-4824-8A97-ACFF7521CEF5@.microsoft.com...
> Hi All ,
> I have some concerns with replication
> 1. if the replication fails 1/2 way , does that mean some data is being
> replicated across alrdy or it'll do a roll-back to ensure either it's a
> complete replication or no replication ?
> 2. previously i have already set up the application but in EM , i went to
> Replication --> Publications and delete the publication instead of going
to
> the Replication Monitor --> Publishers --> to delete the publication and
> found that i couldn't delete the publication in Replication Monitor -->
> Publishers any more
> which sp can i used to delete ?
> 3. i got the error from replication "the subscription has been marked and
> must be reintialized . No Sync subscriptions will need to be dropped and
> recreated?
> - why this error occured , i have set for replication for 72 hours
>
> Kindly advise
> tks & rdgs
|||Hi,
I have tried sp_droppublication on the publication db but there's no such
publication to be dropped
when i tried deleting from the replication monitor i got the following
error :
SQL server Enterprise Manager could not retrieve information about
publication 'publication1'
Error 21776 the name 'publication1' was not found in the TransPublication
collection. if the name is a qualified name use [] to seperate various parts
of the name and try again
how could i resove this ?
kindly advise
tks & rdgs
"Hilary Cotter" wrote:

> 1) this depends. If there is a problem deploying the snapshot, it will be
> reapplied, but not rolled back. So if you don't reapply the snapshot after
> failure your subscriber database will have some of the replicated objects
> and replication metadata in place. If the merge or distribution agent fails
> midway it depends on the transactional boundary. Transactional replication
> replicates transactions transactionally. So if a transaction with 200
> commands (for instance a transaction which updates 200 rows) fails, it will
> be completely rolled back. If you are replicating a transaction which causes
> a cascading update/delete on the publisher and you have enforced this
> cascade for replication, and this transaction fails, it will be rolled back.
> For merge replication, if a child record is applied before the corresponding
> parent record and the parent is not part of the batch, the agent will fail
> and this row will be rolled back, but the successfully applied rows in the
> batch will remain. Next time you run the merge agent, this transaction
> should succeed if the parent record comes over in the next batch. Merge
> replication does not guarantee durability.
> 2) try sp_droppublication 'publicationname' in the publication database.
> 3) You should set your history retention to the same value of your
> transaction retention (right click on replication monitor, select
> distribution properties, and click on the properties button, and set it
> there).
> --
> 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
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:6A1D3EAE-EE3A-4824-8A97-ACFF7521CEF5@.microsoft.com...
> to
>
>