I have an SSIS package on SQL 2005 that is called from within a stored procedure by running sp_start_job to run the job that launches the SSIS package. It then checks on the run status until the package execution is complete. The package seems to fail occasionally because of deadlocking errors. There's usually no other user transactions running in the database so I think the conflict must be coming from my process somehow. Any idea what could possibly be causing the deadlock error? I appreciate any help that you can provide.