Originally posted by: TRACEYSQL
A process within our Financials which does some calculations and build tables is run for two separate companies. I have seen the deadlock occur whilst both run at the same time and then i seen the first run and second is run without no deadlock and the 2nd has to wait until first finishes even when the data is different.
Generally if deadlock happens infrequently just rerun the terminated job.
However, since "financial" processing involved, I would either reengineer or schedule them so they don't interfere with each other. As already noted in this thread, SQL Server 2005 deadlock graph is an excellent tool to resolve deadlocks.
The 2nd waiting for 1st to finish condition very likely indicates table lock by the 1st.
Kalman Toth - Database, Data Warehouse & Business Intelligence Architect
SQL Server 2005 Training, SSAS, SSIS, SSRS: http://www.sqlusa.com/