locked
Would the deadlock have caused the replication to run slower than usual RRS feed

  • Question

  • transaction replication runs fine and no error found, however in error log deadlock details are captured. so my question is Would the deadlock have caused the replication to run slower than usual?
    Wednesday, December 30, 2015 1:02 PM

Answers

  • I dont think so.

    Deadlock means two process locks each other and one is rolled back as it is chosen as a victim. Which means by the time u find that there was a deadlock one of the process is rolled abck and other is running as normal , so how can it cause slowness?

    Ur replication slowness would be due to some other reason.

    Check this blog to find out how to troubleshoot transactional replication slowness

    http://blogs.msdn.com/b/chrissk/archive/2009/05/25/transactional-replication-conversations.aspx


    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

    Wednesday, December 30, 2015 2:32 PM

All replies

  • yes...

    capture deadlock information using

    http://www.mytechmantra.com/LearnSQLServer/Identify-Deadlocks-in-SQL-Server-Using-Trace-Flag-1222-and-1204/


    Please click Mark As Answer if my post helped.


    • Edited by AV111 Wednesday, December 30, 2015 1:18 PM
    Wednesday, December 30, 2015 1:17 PM
  • I dont think so.

    Deadlock means two process locks each other and one is rolled back as it is chosen as a victim. Which means by the time u find that there was a deadlock one of the process is rolled abck and other is running as normal , so how can it cause slowness?

    Ur replication slowness would be due to some other reason.

    Check this blog to find out how to troubleshoot transactional replication slowness

    http://blogs.msdn.com/b/chrissk/archive/2009/05/25/transactional-replication-conversations.aspx


    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

    Wednesday, December 30, 2015 2:32 PM