Problem:-
The snapshot files for a transactional publication are
immediately removed after being generated by the snapshot agent.
Noticed that status of the publication articles are 3.
Which is wrong either they should be 0 = Inactive, 1 = Subscribed or 2 =
Active.
Solution :-
1) Delete the
subscription and publication.
2) Check the
tables to see if there are still rows for the publication database available:
select * from msdb..MSdistpublishers
select * from distribution..MSpublisher_databases
select * from distribution..MSarticles
where publisher_db =
'distribution'
select *
from distribution..MSsubscriptions
where publisher_db =
'distribution'
3) Delete all
rows that have still the 'publisher_db' from the just deleted publisher
database:
delete from distribution..MSarticles where
publisher_db = 'distribution'
delete from
distribution..MSsubscriptions where publisher_db = 'distribution'
4) Re-create the
publication subscriber and initialize.
Help Links :-
After applied the below
ReplyDeletedelete from distribution..MSarticles
delete from distribution..MSsubscriptions
check if the replication start to pick up otherwise, delete and recreate the replication (make sure that tables are empty)
The original post on this topic was for a SQL Server 2005 instance but this process worked for our SQL Server 2012 instance
ReplyDeleteexcellent solution. saved our day...
ReplyDeleteexcellent solution, saved our day.
ReplyDeleteAnother factor to consider is the expense of scalability related with restrictive programming. upgrade computer hardware
ReplyDelete