title: Force sequential execution in stored procedure
body: <p>We have a stored procedure that executes a number of selects and updates on various tables.  This stored procedure is being called within an SSIS package.  It is only called once.  I can see in the execution plan (and in my trace) that the queries are executing in parallel.  This isn't an issue when volume is low but when data volume is high, the statements are causing deadlocks and the package fails due to deadlock.  I thought to Set the lock timeout in the SP but I'd prefer to force sequential execution of the updates if possible.  Any help suggestions on how to force sequential execution within the stored procedure would be a great help.</p>