none
replmon - snapshot

    Question

  • Hi guys,

    I got a SQL Server 2014 SP2 with a transactional replication on it.

    The replication itself works fine but when I need to take snapshots i get the following problem:

    If I start a single snapshot agent (in Replication Monitor or Job Activity Monitor or per TSQL), the replication monitor shows (sometimes!) that another (random!) snapshot agent is started too - but it really isn't (Job Activity Monitor Shows status idle).

    The snapshot agent I started runs normally and as expected. The second one that seemed to be started fails after 10 minutes saying: "the replication Monitor has not logged a Progress message in 10 minutes. this might indicate ..." - well, it really didn't run so it fails showing this error.

    This phenomenon doesn't really affect my work but I don't like seeing all those red crosses in my replication monitor.

    Any ideas?

    Thanks in advance

    Diese

    Thursday, January 12, 2017 10:37 AM

All replies

  • Hi Diese,

    Does this Snapshot Agent has a schedule? Can you check Job property and schedule information. I do not think think ideally you should be running snapshot agent so frequently in transnational replication until unless you want to re-initialise the subscription from fresh snapshot.

    Thanks,


    Kindly mark the reply as answer if they help

    Thursday, January 12, 2017 12:26 PM
  • Sometimes your snapshot history gets messed up if you shut down one of your agents or kill them. This will clear in time as your snapshot history is purged. In the mean time you need to determine what your snapshot agent is doing. The best way to do this is to right click on your publication in the replication folder in Management Studio (not in replication monitor) and select view snapshot agent status.

    If you do see the message "the replication Monitor has not logged a Progress message in 10 minutes. there - this likely indicates that you are experiencing blocking with user processes. You will need to investigate this and determine if you should stop and rerun the snapshot or kill user processes so that snapshot can finish.

    Thursday, January 12, 2017 12:35 PM
    Moderator
  • Hi Sunil,

    thanks for the answer.

    I do not schedule my snapshot agents and I do only reinitializations, when I add new articles to the publications.

    In my environment I have to add new articles about every two weeks - so I need to run the snapshot agents.

    Thursday, January 12, 2017 2:47 PM
  • Hi Hilary,

    thanks for the answer.

    As said before the 2nd snapshot Agent - seems to be started - but it didn't. It's only the replication Monitor that thinks I started 2 Snapshot agents at one time.

    The "view snapshot Agent status" overview, the activity Monitor, snapshot Agent history don't Show any activity of this 2nd Agent.

    Thursday, January 12, 2017 3:09 PM
  • Sounds like you are good then.
    Thursday, January 12, 2017 9:01 PM
    Moderator
  • Hi Diese,

    Do you have a large database you've got replication enabled on?

    Thursday, January 12, 2017 9:12 PM
  • Hi Sunit,

    my Database is about 270 GB, tables and Indexes are page compressed.

    Btw I got 2 Environments (TEST / DEV) atm where I got the same Database, same replication configured, same Agent Profile Settings, [...]. Only the Hardware is different.

    Still the same phenomenon.

    Wanted to resolve this before go live.

    Friday, January 13, 2017 7:18 AM