Post reply

Replication: Distribution Agent Monitoring

  • October 3, 2013 at 12:13 am

    #298439

    Comments posted to this topic are about the item Replication: Distribution Agent Monitoring

  • October 3, 2013 at 4:32 am

    #1655488

    This is excellent. Think I'll probably get some good use out of this query. Will post again if I notice any issues.

  • October 3, 2013 at 6:53 am

    #1655542

    Nice article Brian. Thanks for sharing.

    Sujeet Singh

  • October 3, 2013 at 10:05 am

    #1655627

    Good stuff Brian!

  • October 3, 2013 at 12:18 pm

    #1655661

    Thanks so much for sharing this! We've just implemented SQL Server Replication a week or so ago and I'm sure that this will help tremendously going forward.

  • October 3, 2013 at 12:24 pm

    #1655663

    Excellent! We have Replication latencies several times a day on our daisy-chain system (Production-to-Reporting-to-DataMart) and this proc found the bottlenecks.

    Three thumbs up.

  • October 5, 2013 at 2:35 pm

    #1656111

    Hi Everyone,

    Since this thread is going on with replication I want to clarify some issues that I am facing in my project

    In our project we have concept of DB mirroring (replication) of OLTP data from one core db server to target db server

    Also, we are using using for our SAP BO reporting purposes. Now sometimes the problem happen is in one the SAP BO report part of the data is not updated into cubes after cube refresh is done, it is delaying the same data to update after 24 hours once the process to update cubes run

    So, once we analyzed we found that it is not the problem in queries as we tested the same scenario in development and the data is updating after first set of run / cube refresh

    Then the thought come to our mind is that sometimes we got alert like replication is not bringing data into database for some sort of minutes through the alert that is configured for replication

    Now, my question is suppose the replication is replying the data for sometime and then it started working automatically and the data suppose within that time happens / transacts in core db will be reflected in mirror db properly or not once it starts working

    As we are thinking for the root cause for the report data inaccuracy is somewhat related to db mirroring only

    Kindly let me know your valuable feedback on this peculiar issue

  • October 9, 2013 at 6:50 pm

    #1657354

    Thanks for sharing. Very nice. Looking to use in our environment.

  • October 14, 2013 at 11:05 am

    #1658312

    Will this code work on systems where publisher, distribution and subscriber databases have been on individual servers ?

  • October 14, 2013 at 1:09 pm

    #1658334

    Yes. The code is based on the system tables in the distribution database. So you just need to run it on your distribution server.

    Good luck!

  • October 14, 2013 at 3:24 pm

    #1658360

    It's fantastic !! running likea charm.. Thank you very much bro for sharing us the invaluable script !! 😎

  • January 2, 2014 at 10:27 am

    #1676995

    BUG FIX:

    Hi all,

    I recently discovered a bug in the get_distribution_status code (missing predicate) that incorrectly reported cmd_tbd/blk values when replication is configured for multiple publisher databases. The latest version (2.4) has been updated with the fix, plus a few performance enhancements, and re-posted with the article.

    Thanks,

    -Brian

  • January 2, 2014 at 10:29 am

    #1676996

    .

  • September 11, 2015 at 5:17 pm

    #1826176

    Thank you for the article!

    Has anybody trying using this on SQL Server 2014? I did and it returns no records.

Viewing 14 posts - 1 through 13 (of 13 total)

You must be logged in to reply to this topic. Login to reply