Replicated database deadlocks.

    General discussion

  • We have a production database that sits on server1.

    This database has transactional replication. There is a replicated database that sits on server2. On server2 there are other databases that READ from the replicated database.

    Our admins have noticed that there are deadlocks getting created in the replicated database. So the developers have requested for a second replicated instances. This request has been turned down with a note - Another replicated instance would put a load on the production database that sits on sqlserver1.

    How do you collect stats to prove or disprove this statement?

    This is SQL Server 2008 (not R2)
    • Edited by c-sharp-coder Friday, March 28, 2014 6:06 PM version of sql server.
    Friday, March 28, 2014 6:00 PM

All replies

  • First, you should not have deadlocks on read.  This would be a result of your snapshot isolation level.  Before doing anything, you should look at that.

    Second, having a 2nd subscriber to a database has no impact at all on the source server.  It simply delivers the data to 2 destinations instead of 1.  In addition, this will in no way fix your problem.

    Friday, March 28, 2014 6:10 PM