none
Database not synchroizing in replication?

    Question

  • Database not synchronizing cause of subscriber log file is full.

    1.Please share  solutions!

    2.How many ways monitor replication ?

    3.pre-check list to identify problems in replication

    4. how to reinitialize snapshot

    5. share any links regarding replication and troubleshooting..

    6. how to restart agnets.

    Thanks in Advance

    Vijay

    pls

    Saturday, January 18, 2014 5:07 AM

Answers

  • 1) OK

    2) replication monitor is best for a visual inspection of the status of your publications and subscriptions. I email new entries to the msrepl_errors table to myself via a trigger.

    3) Right click on your failed subscription in replication monitor and select View Details. The error will be listed in the bottom half of the dialog. Address the issue if possible. Note that if the cause of the error is not obvious set up your agents from logging and examine the log. http://support.microsoft.com/kb/312292/en-us

    4) In Management Studio, drill down on the publication, expand it and right click on the subscription and select Reiniitalize. You might need to do this on the subscriber in the local subscription node. Then select the option to use a new snapshot or the exisitng snapshot. Check your snapshot agent (in replication monitor) to see if it is running or if it has run recently. Then start up your merge or distribution agent.

    5) https://www.google.com/#q=sql+server+replication

    6) You can normally restart them in replication monitor.


    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

    • Marked as answer by vijay_1234 Saturday, January 18, 2014 2:56 PM
    Saturday, January 18, 2014 1:23 PM

All replies

  • Database not synchronizing cause of subscriber log file is full.

    1.Pls share how to solutions!

    2.How many ways monitor replication ?

    3.pre-check list to identify problems in replication

    4. how to reinitialize snapshot

    5. Pls share any links regarding replication and troubleshooting..

    6. how to restart agnets.

    Thanks in Advance

    Vijay

    pls

    Saturday, January 18, 2014 5:03 AM
  • 1) OK

    2) replication monitor is best for a visual inspection of the status of your publications and subscriptions. I email new entries to the msrepl_errors table to myself via a trigger.

    3) Right click on your failed subscription in replication monitor and select View Details. The error will be listed in the bottom half of the dialog. Address the issue if possible. Note that if the cause of the error is not obvious set up your agents from logging and examine the log. http://support.microsoft.com/kb/312292/en-us

    4) In Management Studio, drill down on the publication, expand it and right click on the subscription and select Reiniitalize. You might need to do this on the subscriber in the local subscription node. Then select the option to use a new snapshot or the exisitng snapshot. Check your snapshot agent (in replication monitor) to see if it is running or if it has run recently. Then start up your merge or distribution agent.

    5) https://www.google.com/#q=sql+server+replication

    6) You can normally restart them in replication monitor.


    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

    • Marked as answer by vijay_1234 Saturday, January 18, 2014 2:56 PM
    Saturday, January 18, 2014 1:23 PM
  • Thanks Hilary.

    Saturday, January 18, 2014 3:31 PM