SQL Server Performance

How to rub job without deadlock

Discussion in 'General DBA Questions' started by tnthieu, Aug 14, 2006.

  1. tnthieu New Member

    Hi all,

    I have 2 servers, ex. A & B. When users update somethings in A, I will create jobs to reflect the changes to B. Because there are many jobs running at the same time, ex. insert many things into one table, deadlock happens. Do you have any suggestion for this issue?
    Can I run the job sequently, or use transaction in job, or.....?????

    Thank you,
  2. deepakontheweb New Member

    You should consider using SQL Replication in this scenario <img src='/community/emoticons/emotion-1.gif' alt=':)' /><br /><br />Using it you can define tables for that data should be replicated from Server A to Server B. its hazzle free task compared to setting up your own jobs.<br /><br /><br /<a target="_blank" href=http://www.sql-server-performance.com/transactional_replication.asp>http://www.sql-server-performance.com/transactional_replication.asp</a><br /<a target="_blank" href=http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx>http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx</a><br /><br /><b>Deepak Kumar</b><br /><font size="1">MVP, MCDBA - SQL Server<br /><br />Disclaimer: This post is provided as is with no rights & warranty for accuracy, for the sake of knowledge sharing only.</font id="size1">
  3. dineshasanka Moderator

    is there any specific reason to you to run jobs instead of Replication or DTS


Share This Page