Results 1 to 10 of 10
  1. #1
    Join Date
    Apr 2004
    Posts
    49

    Unanswered: How to detect replication doesn't work and get noticed?

    I want to get notice by netsend, email or any other methods
    when replication doesn't work or malfunction.

    Does anyone know how to do this or any other solution you use for this kind of issue?

    Thank you..
    MCSD .NET, SCJP, SCJWD

  2. #2
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    Every agent that runs your replication (snapshot, logreader, distributot, and queuereader) have associated SQLAgent jobs. All you have to do is modify those jobs by going to Notification tab of the job properties and selecting notification method you'd like to get. You should have an appropriate operator set up before, or you can do it right there by selecting New Operator.
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

  3. #3
    Join Date
    Apr 2004
    Posts
    49
    Thank you for reply..

    The main problem I have is how to find out if the replication doesn't work..
    I can notice with agent history or icon.

    Sometimes the icon become X marked, some times agent keep trying to connect and generate error with forever loop, sometimes gives I/O error while working..

    How to find out these and what's best way to find out if replication doesn't work properly?
    MCSD .NET, SCJP, SCJWD

  4. #4
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    Have you looked at what I posted about?
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

  5. #5
    Join Date
    Apr 2004
    Posts
    49
    Yes I did..
    I knew that part..
    Could you give me more detail with example with specific error cases?
    Then, I understand more clearly.
    MCSD .NET, SCJP, SCJWD

  6. #6
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    see attachment
    Attached Thumbnails Attached Thumbnails Job Notification Tab.bmp  
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

  7. #7
    Join Date
    Apr 2004
    Posts
    49
    Thank you for the image..
    I think I got it at this level..

    I just wonder is there a way to run a custom application when job fails rather than sending Net-send..

    Since I have to check hundreds of systems replicated, if I use net-send I will get too much of it and hard to maintain.
    If I can run my custome application reporting problem organized, it will be easy to maintain.
    MCSD .NET, SCJP, SCJWD

  8. #8
    Join Date
    Sep 2003
    Location
    KY
    Posts
    146

    Well

    In that case you should create a batch file and call it from task window .

    In SQL Scheduler when you click on the task and click advanced it says

    " On failure action: and then there is a drop down . All you have to do is add another task to the existing job and call it here

    It will say

    "On failure Action : Goto Step #2" In that step #2 you can all the windows batch file .. (which can contain anything like ISQL, another program ...)
    Attached Files Attached Files

  9. #9
    Join Date
    Apr 2004
    Posts
    49
    Thank you!
    I got it!
    MCSD .NET, SCJP, SCJWD

  10. #10
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    Another way of doing it would be to create a custom alert and a scheduled task. When conditions for the alert are met you can invoke that scheduled task that may contain ... see previous post.
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •