Post reply

Transactional replication

  • July 17, 2008 at 5:08 pm

    #122418

    [highlight=#ffff11]Hi everyone,

    I have transactional replication set up running on SQL server 2005 Ent. 64 bit edition(3 servers, different server for publisher, distributor and for subscriber) However not too long ago a job running on subscriber disappeared. I luckily caugth that early and resubscribed for the same publication. However the same thing happened with another job the other day overnight and some data was missing on subscriber and end users notified me. I would like to know if anyone has seen the similar issue on the subscriber where replication job disappeared and what you did to fix and or detect this? Thanks

  • July 18, 2008 at 3:45 am

    #844877

    We have never seen or come across such incidents.

    Best thing you can do is capture the necessary info by capturing trace through profiler. In future if the same thing will happen you can catch it.

    I am sure if it's happening it will happen again.

    ---------------------------------------------------
    "Thare are only 10 types of people in the world:
    Those who understand binary, and those who don't."

  • July 18, 2008 at 2:32 pm

    #845259

    thanks for the reply, no matter how the jobs started disappearing the process must be using sp_delete_job proc. I will run a trace for watching the proc above.

    Have a nice day..

    Bulent

  • July 18, 2008 at 2:58 pm

    #845267

    Bulent Gucuk (7/18/2008)

    thanks for the reply, no matter how the jobs started disappearing the process must be using sp_delete_job proc. I will run a trace for watching the proc above.

    Have a nice day..

    Bulent

    If someone is calling sp_dropsubscription or sp_droppullsubscription you will get that effect!


    * Noel

  • July 18, 2008 at 4:12 pm

    #845290

    Thanks Noel, I will also add those procs to my trace.

    Have a nice day...

    Bulent

Viewing 5 posts - 1 through 4 (of 4 total)

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