Quantcast
Channel: SQL Server Replication forum
Viewing all articles
Browse latest Browse all 4054

setup transactional replication with pull subscription using the option @allow_initialize_from_backup

$
0
0

I am trying to setup  transactional replication with pull subscription using the option @allow_initialize_from_backup = true and I am a bit confused on steps involved because at teh end of setup it shows ‘uninitialized subscriber’ in replication monitor.

Publisher, distributor and subscriber are three separte SQL server 2008 R2 servers.

I executed below steps -

  1.       On publisher SQL server executed sp_addpublication with  options @immediate_sync ='true and   @allow_initialize_from_backup = true  
  2.       On publisher SQL server executed  sp_addarticle to add the articles
  3.       On distribution  SQL server disabled distribution cleanup agent and stopped the distribution cleanup job
  4.       On publisher SQL server created full backup of the publication db
  5.       On subscriber SQL server restored above backup with recovery
  6.       On publisher  executed  sp_addsubscription using options  @subscription_type = N'pull', and @sync_type = N'initialize with backup'
  7.       On subscriber  executed  sp_addpullsubscription  using options  @independent_agent = N'True',@subscription_type = N'pull',@description = N'',@update_mode = N'read only',@immediate_sync = 1
  8.       On distribution  SQL server enabled distribution cleanup agent and started the distribution cleanup job

At the end of these steps it shows ‘uninitialized subscriber’ in replication monitor.  What am I doing wrong ?

 In the above steps what is the difference between sp_addsubscription and sp_addpullsubscription ? 

When I setup transactional replication with push subscription using the option @allow_initialize_from_backup = true, I only execute sp_addsubscription on publisher.


Ravi Kumar



Viewing all articles
Browse latest Browse all 4054

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>