Entrar
 
HomeBibliotecaWikiAprenderGaleriaDownloadsSuporte ComunidadeFóruns
Recursos para Profissionais de TI >
> 
> 
Replication commands are not getting executed at subscriber

Respondido Replication commands are not getting executed at subscriber

  • segunda-feira, 7 de maio de 2012 13:50
     
     
    Entrar para Votar
    0

    Hello All, 

    We were publishing  list of tables from publisher to subscriber, what we see is that  some of the tables  data are getting replicated exactly  but one of the table  ( tblLoggerDetails)  the  data is not getting replicated at the subscriber. 

    We checked the distributor and the commands are coming there but not getting executed at the subscriber it seems. 

    Then what we have done is , we have deleted the existing subscription and added the fresh one  and  data started getting replicated even the  old one . 

    1. Can  someone what was the issue ? Do only adding fresh subscription and deleting the old one is only solution ? 

    2. The table which i am talking is used by window service application which will keep inserting the records in this table.  So is this is any locking issue ? 

    3. When should we publish the data , is this  during non-business hours ? 

    Regards,

    Phani


     

Todas as Respostas

  • segunda-feira, 7 de maio de 2012 14:14
     
     
    Entrar para Votar
    0
    Hey Phani - what was replication monitor ahowing for the subscription that was not being pushed?  Also was the subscription set up to run continuous or on an interval?  You should be able to look at the subscription details in replication monitor to see if there was an error in applying the transactions, my other guess is that the agent was not running.  Is this transactional replication?


    Convert DTS to SSIS | Document SSIS | 30+ SSIS Tasks | Real-time SSIS Monitoring | Quick Starts | BI Blitz

     
  • segunda-feira, 7 de maio de 2012 15:04
    Moderador
     
     
    Entrar para Votar
    0

    The commands should be being replicated to the subscriber. There are certain events on SQL 2005 which would cause the commands to be not picked up by the log reader agent. There is also a condition when the publication or new article addition gets locked, and then killed and your subscription will be placed in a not active status.

    What version are you running?

    To answer your questions

    1) With the subscription being recreated it is impossible to figure out what has happened. There may be messages in the SQL Server log or the windows event log complaining about job failures which you may want to investigate.

    2) No, on the publisher this will not be a problem as the log reader will read the log asynchronously and not be affected by changes occurring on the published table.

    3) You may want to generate the snapshot on non-production hours as snapshot generation may place locks on the table which will lock with user activity. However once the snapshot is generated you can replicate at any time with little affect on user activity on the publisher.

    looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

     
  • terça-feira, 8 de maio de 2012 05:46
     
     
    Entrar para Votar
    0

    Thanks for the quick response. 

    We are using the SQL Server 2008 R2 version. Subscription is contiguously.

    We are not going for the snapshot option, we are doing the initial backup and  then starting replication.  Is this cause issues ( Our DB size is 200 GB , can we go for transaction replication  with snapshot for this or intial back up is correct option ?)

    There was never any job failure

     

     
  • terça-feira, 8 de maio de 2012 13:27
    Moderador
     
     Respondido
    Entrar para Votar
    0

    The initialize from backup option is probably a good fit here.

    However there are issues when you add a table to a publication after you have initialized from a backup. I have been unable to repro these issues but have worked on cases with them.

    Can you remove this article from the publication and create a new publication and subscription with just this table and then do not select the initialize from backup option for this publication/subscription pair.

    looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941